In a Documentum repository users are uniquely identified by the user_name attribute. Being a key, the user_name value is used in related objects (for example: owner, r_modifier, r_creator, r_lock_owner, etc.) stating that this user performed an action on this object.
In certain cases we need to change the user_name value: for example when we want to create a new user, but an old one (perhaps deactivated) already exists with the same user_name.
Being a key, we can't simply update this value, you won't even be able to modify it on user property screen. Here are the ways to accomplish this:
1. Manual renaming
There's a simple tool called Reassign User which invokes the dm_UserRename job (Renaming users - how dm_UserRename job works explains how this job works):
a. (Optional) Create a new user with the user_name you want to rename the old user to.
b. Open DA, go to Users node in browsertree, find the desired user, right click on it and choose Reassign User. On the opened page enter/select the new user, select the option to run the reassign job now (and change other settings if required).
c. (Optional) As soon as the dm_RenameUser job has completed, you can remove the original (old) user if it's not needed anymore.
Note that you can skip the creation of a new user and just enter the new user_name on the Reassign User page, it will handle the modification of user_name itself.
2. Automatic renaming
If we want to rename many users, the manual approach would be really annoying, so as usual we turn to some DFC coding.
Renaming users in DFC is quite straightforward, it's enough to call the rename method:
IDfUser user = session.getUser("userA");
user.renameUser("userB", true, false, true);
user.save();
Here's the method description from the API:
void renameUser(String userName,
boolean isImmediate,
boolean unlockObjects,
boolean reportOnly)
throws DfException
Renames this user. If this is a new user, the attribute value is set. If this is an existing user, this method invokes a job to rename user.
Parameters:
userName - user name to be set or renamed to (existing user)
isImmediate - Detemines if the job should be run immediately or run on schedule.
unlockObjects - control if the objects should be unlocked when renaming user. If this is a new user, this parameter does not take any effect.
reportOnly - control if the job created is to report or actual rename. If this is a new user, this parameter does not take any effect.
In certain cases we need to change the user_name value: for example when we want to create a new user, but an old one (perhaps deactivated) already exists with the same user_name.
Being a key, we can't simply update this value, you won't even be able to modify it on user property screen. Here are the ways to accomplish this:
1. Manual renaming
There's a simple tool called Reassign User which invokes the dm_UserRename job (Renaming users - how dm_UserRename job works explains how this job works):
a. (Optional) Create a new user with the user_name you want to rename the old user to.
b. Open DA, go to Users node in browsertree, find the desired user, right click on it and choose Reassign User. On the opened page enter/select the new user, select the option to run the reassign job now (and change other settings if required).
c. (Optional) As soon as the dm_RenameUser job has completed, you can remove the original (old) user if it's not needed anymore.
Note that you can skip the creation of a new user and just enter the new user_name on the Reassign User page, it will handle the modification of user_name itself.
2. Automatic renaming
If we want to rename many users, the manual approach would be really annoying, so as usual we turn to some DFC coding.
Renaming users in DFC is quite straightforward, it's enough to call the rename method:
IDfUser user = session.getUser("userA");
user.renameUser("userB", true, false, true);
user.save();
Here's the method description from the API:
void renameUser(String userName,
boolean isImmediate,
boolean unlockObjects,
boolean reportOnly)
throws DfException
Renames this user. If this is a new user, the attribute value is set. If this is an existing user, this method invokes a job to rename user.
Parameters:
userName - user name to be set or renamed to (existing user)
isImmediate - Detemines if the job should be run immediately or run on schedule.
unlockObjects - control if the objects should be unlocked when renaming user. If this is a new user, this parameter does not take any effect.
reportOnly - control if the job created is to report or actual rename. If this is a new user, this parameter does not take any effect.
