Details on renaming a person

Here are details on the "how, why, where, and when" of each request involved with renaming a person.

Move Person's Name in Hierarchy

• Triggered by: Choosing "Actions - Rename Person" then "Request Move to New Certifier" in the Public Address Book.
• Posted on: The server where you choose the rename action.
• Carried out on: The server from which you choose "Actions - Complete Move."
• Carried out: When you choose "Actions - Complete Move" to move a person's name to another hierarchy.
• Result: Approves the move and triggers the "Initiate Rename in Address Book" request.

• Triggered by: Choosing a rename action. For a person name move to a different name hierarchy, choosing "Action - Complete Move" is also required to trigger the request.
• Posted on: The server where you choose the rename action.
• Carried out on: The administration server for the Public Address Book.
• 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 Person document. Prompts the person to accept the new name upon next server access.

• Triggered by: Person accessing a server and accepting the new name.
• Posted on: The first server the person accesses that has the change request in the person's Person document.
• Carried out on: The administration server for the Public Address Book.
• Carried out: According to the Interval setting for the Administration Process in the Server document.
• Result: Updates the person's name in the Public Address Book except in Person documents.

• Triggered by: Completion of the "Rename Person in Address Book" request.
• Posted on: The administration server for the Public Address Book.
• Carried out on: The administration server for the Public Address Book.
• Carried out: According to the "Execute once a day requests at" setting for the Administration Process in the Server document.
• Result: Updates the name in Public Address Book Person documents.

• Triggered by: Completion of the "Rename Person in Address Book" request.
• Posted on: The administration server for the Public Address Book.
• 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.

• Triggered by: Completion of the "Rename in Person Documents" request on the administration server for the Public Address Book.
• Posted on: The administration server for the Public Address Book.
• 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 and Author fields of databases for which it is an administration server and that have the advanced ACL option "Modify all Reader and Author fields" selected.

• Triggered by: Expiration of the period in which a person can accept a new name, by default 21 days. You can use the NOTES.INI setting Name_Change_Expiration_Days to change the expiration period.
• Posted on: The administration server for the Public Address Book.
• Carried out on: The administration server for the Public Address Book.
• 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 from the Person document.