 | Roadmap of Administration Process Requests: Renaming a person or converting a person to hierarchical
[return to the Roadmap Administration Process Requests main article]
 
Level:
Works with:
Updated:
Inside this article:
Related links:
Get the PDF:
|  | You can use the Administration Process to change a person's common name, move a person to a different branch of an organization hierarchy (or to a different organization), or upgrade the person from flat to hierarchical. Each of these tasks is considered a renaming and involves the same series of requests with one exception: moving a person to a different hierarchy generates a "Move Person's Name in Hierarchy" request; this request, which requires your approval, doesn't occur with the other rename tasks.
The following sequence of requests occurs when you rename a person:
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.
Initiate Rename in Address Book
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.
Rename Person in Address Book
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.
Rename 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.
Rename in Access Control List
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.
Rename in Reader/Author Fields
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.
Delete Obsolete Change Requests
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.
[go on to the Converting servers to hierarchical naming task]
[return to the Roadmap Administration Process Requests main article]
Copyright 1997 Iris Associates, Inc. All rights reserved. |