Rename person

Move person's name in hierarchy

Triggered by: Choosing Actions > Rename Person then Request Move to New Certifier in the Domino® Directory or by choosing People > Rename from the Tools pane of the Domino® Administrator.

Carried out on: The server from which you choose Actions > Complete Move.

Carried out: When you choose Actions > Complete Move, in the Name Move Requests view of the Administration Requests database, to move a person's name to another hierarchy.

Result: Approves the move and triggers the Initiate rename in Domino Directory request.

Initiate® rename in Domino® Directory

Triggered by: Choosing a rename action.

Carried out on: The administration server for the Domino® Directory.

Carried out: According to the Interval setting for the Administration Process in the Server document.

Result: Adds the new name, certificate, and change request to the user's Person document. Prompts the user to accept the new name upon next server authentication.

Rename person in Domino® Directory

Triggered by: Person accessing a server and accepting the new name.

Carried out on: The administration server for the Domino® Directory.

Carried out: According to the Interval setting for the Administration Process in the Server document.

Result: Updates the user's name in his or her Person document and in groups in the Domino® Directory. Posts the Rename in Person documents and the Rename person in Unread Lists administration requests.

Rename in Person documents

Triggered by: Completion of the Rename person in Domino Directory request.

Carried out on: The administration server for the Domino® Directory.

Carried out: According to the Execute once a day requests at setting for the Administration Process in the Server document.

Result: Updates the user's name in Domino® Directory Person documents other than the user's own Person document. For example, if the user is an administrator, the name may appear in the Owner or Administrator field of another user's Person document.

Rename person in unread list

Triggered by: Completion of the Rename person in Domino Directory request.

Carried out on: Each server in the domain.

Carried out: According to the Execute once a day requests at setting for the Administration Process in the Server document.

Result: Each server in the domain examines every database on the server and updates the person's name in any unread lists.

Rename in Access Control List

Triggered by: Completion of the Rename person in Domino Directory request.

Carried out on: Each server in the domain.

Carried out: According to the Interval setting for the Administration Process in the Server document.

Result: Each server in the domain updates the person's name in ACLs of databases for which it is an administration server. In Domino® 6 only, also updates the name in shared folders, views, agents and forms.

Rename in Design Elements

Triggered by: Completion of the Rename in Access Control Lists request on the administration server for the Domino® Directory.

Carried out on: Each server in the domain.

Carried out: According to the Delayed Request Settings on the Server Tasks -- Administration Process tab in the Server document.

Result: Each server in the domain updates the person's name is in shared design elements of databases for which it is an administration server. Private design elements are not renamed.

Rename person in Free Time Database

Triggered by: Completion of the Rename person in Domino Directory request.

Carried out on: The person's home server.

Carried out: Immediately

Result: The person's name is changed in the Calendaring and Scheduling Free Time Database.

Rename person in calendar entries and profiles in mail file

Triggered by: Completion of the Rename person in Free Time Database request.

Carried out on: The person's home server.

Carried out: Immediately

Result: The person's name is changed in their mail file's Calendar Profile and appointment documents. If the person's common name was changed and the common name is in the title of the mail file, the mail file title changes to reflect the new name. The name is also changed if it exists in the Chair field of future meeting invitations.

Rename person in calendar entries and profiles in mail file extended

Triggered by: Completion of the Rename in Person documents request.

Carried out on: Each server in the domain.

Carried out: As a Delayed Request.

Rename in Reader / Author Fields

Triggered by: Completion of the Rename in Person documents request on the administration server for the Domino® Directory.

Carried out on: Each server in the domain.

Carried out: According to the Delayed Request Settings for the Administration Process in the Server document.

Result: Each server in the domain updates the person's name in Reader / Author fields of databases for which it is an administration server and that have the advanced ACL option Modify all Reader / Author fields selected.

Delete Obsolete Change Requests

Triggered by: Expiration of the period in which a person can accept a new name, by default 21 days. When you rename the person, you can change the expiration period.

Carried out on: The administration server for the Domino® Directory.

Carried out: According to the Execute once a day requests at setting for the Administration Process in the Server document.

Result:The Administration Process deletes the word Pending from the Change Request field of the Person document.

Timing for Rename a user request