Recently refreshed design of RESOURCE Reservations DB for my customer. User wants to delete a resource, but afterwards user needs me to manually delete the resource in ADMIN P.For some reason, whatever task has to run to do this will not update in ADMIN P.
I have signed the 4 required agents needed in RESOURCE RESEVATIONs and they run without error.
The next step in the delete process is to Delete the mail-in document form the directory. Only an administrator can do that, so the second step is to approve the deletion of the document. Its worked this way from the beginning,
After you create a Resource document, the information that you can change includes the Availability Settings, Description, Capacity, Online resource data, Other Comments, and Ownership Options fields. To change any other information about the resource, you must delete the Resource document and then create a new one containing the new information.
New resource information is not available until the Administration Process updates the Resource document in the IBM® Lotus® Domino® Directory and the change replicates to all relevant replicas of the Domino Directory that are on servers used for scheduling resources.
If you delete a resource from the Resource Reservations database, an Administration Process Request document for the resource deletion is created in the Administration Requests database (ADMIN4.NSF). To delete the resource and remove it from the Domino Directory, you must open the Administration Requests database and approve the request for deletion. Note that to approve requests you need the appropriate access in the ACL of the Administration Requests database.
We are looking at ways to better notify/remind those who may not have checked the help file that manual Admin approval is required since the delete action is destructive and we want you to be sure of it. Adds are non-destructive so that is why they do not require manual blessing.