In custom Notes applications, user names are typically stored in Reader, Author or Names fields. If the database's ACL has the "Modify all Names fields" setting enabled, AdminP will update the user's name in all Reader, Author and Names fields in accordance with a name change. However, when a user has been terminated, AdminP will remove the user's name completely from all Reader, Author and Names fields. For some applications, this means that important workflow information will be deleted.
For example, user "Jane Smith" uses a Notes-based Expense Report database. Her name is only stored in an Authors field. When she leaves the company, an AdminP deletion request is submitted. If the Expense Report database's ACL has the "Modify all Names fields" setting enabled, AdminP will remove Jane Smith's name from all of the Expense Reports she created. This means that the Expense Reports Jane created will no longer have her name as the author, and Jane's Expense Reports will no longer appear under her name in any of the views.
Of course, Jane Smith's name could also have been stored in a Text field in addition to an Authors field. AdminP does not update non-Names fields. However, if Jane Smith's name is changed to "Jane Doe", AdminP would update the Author field, but not the Text field. The document now has two versions of Jane's name.
Another example of how AdminP's behavior is problematic is an Issues database with an Issues form. This form includes a single AssignedTo field of type Names. When the author creates an Issue document, they select multiple names in the AssignTo field. The names in the AssignTo field need to be retained for audit purposes. Having AdminP change the names in the list is acceptable, but having AdminP remove names from the list effectively destroys required audit information.
In my experience, it is impractical to redesign existing Notes applications so that they can work the unilateral way that AdminP processes deletion requests.
In my opinion, the best way for custom Notes applications to take advantage of the AdminP name change functionality would be if the Action drop-down list in a database's ACL also included an option or check box to the effect of "Process name changes only" or "Ignore user deletions". We would be able to tell AdminP how to process name changes and deletes on a database-by-database basis. Best of all, we wouldn't have to rewrite existing applications.