ADMINISTERING
Delete person - outbound (source) domain
These requests are generated on the outbound domain when the user name on the outbound domain is a flat name and you have specified a non-immediate deletion.
Delete person in Domino Directory
Triggered by: Choosing Actions - Delete Person in the Domino Directory (or clicking Delete Person) and choosing to delay deletion of the name from the Domino Directory. You can also trigger this action by choosing Delete Person when viewing a Person document with the Web Administrator.
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: The Administration Process removes the name from the Domino Directory, except from other people's Person documents, and posts the Delete in Person documents request. If you have created a termination group and set up the administration process to add deleted users to that group, the name is added to that group. Mails the Delete person in Domino Directory administration request to the inbound domain.
Delete in Person documents
Triggered by: Completion of a Delete in person Domino Directory request.
Carried out: According to the Execute once a day requests at setting for the Administration Process in the Server document.
Result: The Administration Process removes the name from other people's Person documents in the Domino Directory.
Delete in Access Control Lists
Triggered by: Choosing to immediately delete all occurrences of the name from the Domino Directory when initiating the Delete action or the completion of a Delete in Domino Directory request (if you chose to delay deletion of the name from the Domino Directory).
Carried out on: Each server in the domain.
Result: Each server in the domain deletes the name from the ACLs of databases for which it is an administration server.
Get file information for delete (only if deleting the mail file)
Triggered by: Completion of the Delete in Access Control List request on the administration server for the Domino Directory (if you chose to immediately delete all occurrences of the name) or completion of the Delete in Domino Directory request (if you chose to delay deleting the name from the Domino Directory). You must also have specified to delete the mail file in which you chose to delete the person.
Carried out on: The deleted person's home server.
Carried out: Immediately
Result: The person's home server creates an Approve file deletion request which provides information about the mail file. This appears in the Pending Administrator Approval view of the Administration Requests database.
Approve file deletion (only if deleting the mail file)
Triggered by: Completion of the Get file information for delete request.
Carried out on: The server on which you approve the request.
Carried out: When you manually approve or reject the request.
Result: If you approve the request, the Administration Process creates a Request file deletion request.
Request file deletion (only if deleting the mail file)
Triggered by: Approving the Approve file deletion request.
Result: Posts a Delete mail file request.
Delete in Reader / Author fields
Triggered by: Completion of a Delete in Access Control List request on the administration server for the Domino Directory (if you chose to immediately delete occurrences of the name from the Domino Directory) or completion of a Delete in Person documents request (if you chose to delay deletion of the name from the Domino Directory).
Carried out: According to the Delayed Request settings for the Administration Process in the Server document.
Result: Each server in the domain deletes the name from 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. The server scans the databases for shared agents signed by the deleted person and for Private Design Elements (folders, views, agents) signed by the deleted person. Shared agents found are reported in the request's Response document. If Private Design Elements are found an Approve deletion of Private Design Elements administration request is posted.
Delete mail file (only if deleting the mail file)
Triggered by: Completion of a Request file deletion request.
Result: The Administration Process verifies that the administrator who approved the deletion has at least Author with Delete documents access to the Domino Directory. Then the Administration Process deletes the file.
Approve deletion of Private Design Elements
Triggered by: Completion of a Delete in Readers/Authors field request and locating Private Design Elements signed by the deleted person in databases on that server.
Carried out on: Any server in the domain.
Carried out: According to the administrator's discretion.
Result: The deletion is approved and the Request to delete Private Design Elements administration request is posted.
Request to delete Private Design Elements
Triggered by: The administrator's approval of the Approve deletion of Private Design Elements administration request.
Result: Posts the Delete Private Design Elements administration request.
Delete Private Design Elements
Triggered by: Completion of the Request to delete Private Design Elements administration request.
Carried out on: The server containing the database with the Private Design Elements.
Carried out: According to the Interval setting in the Administration Process section of the Server document.
Result: Private Design Elements signed by the deleted person are removed from the databases.
Note: If the person requesting the delete action chose to delete all replicas of a mail file, then a Get File Information for deletion request is created and processed by all servers in the domain. This request is posted after completion of the Delete mail file request or the Delete unlinked mail file request. For each replica of the mail file found on servers in the domain, the Approve file deletion, Request file deletion, and Delete mail file request sequence occurs again.
Delete person - inbound (destination) domain
These requests are generated on the inbound domain.
Triggered by: Receipt of a Delete person in Domino Directory administration request from the outbound domain.
Result: Checks for the flat user name in the Domino Directory. If found, posts the Approve delete person in Domino Directory administration request. If not found, posts the Delete in Access Control Lists and the Delete person in Person documents administration requests.
Approve delete person in Domino Directory (only if a matching flat user name is found)
Triggered by: Completion of an inbound Delete person in Domino Directory request on a sent name.
Carried out on: Any server on which you approve the request.
Result: Post a Delete person in Domino Directory administration request.
Delete person in Domino Directory (only if a matching flat user name is found)
Triggered by: Administrator approving the Approve delete person in Domino Directory administration request.
Result: The Administration Process removes the name from the Domino Directory, except from other people's Person documents, and posts the Delete in Person documents request. If you have created a termination group and set up the administration process to add deleted users to that group, the name is added to the group.
Delete person in Person documents
Triggered by: Completion of a Delete person in Domino Directory request.
Triggered by: Completion of the Delete person in Domino Directory request.
Triggered by: Completion of a Delete in Access Control List request on the administration server for the Domino Directory.
Approve Deletion of Private Design Elements
Request to Delete Private Design Elements
Delete person - cross domain administration request
If you select Immediate processing, the outbound domain has the following subset of requests: