User Admin - Delete user/workflow data from database.

[ustevens]

There is no limit to how much user or workflow (BA,WT,Status/Queue etc) that can be entered into Chorus which results in large databases.  Allow for an easy way to identify data no longer being used that could be triggered for deletion for long serving clients.

[Karen_Hunter]

Different admin configuration components have different requirements.  Please comment on the following observations with expectations, use cases, and priorities.

1. Users administration must be improved to support identity management.  Activation and Deactivation of accounts for licensing and compliance have already been scoped.  Purging configuration information about a user account should become automatic.  Administrators should be able to show active, inactive, or all users for administrative purposes.  Deleting those accounts becomes one of compliance because it removes visibility to the name of the account previously attached in any history and reporting records.
2. Workflow administration must be improved to support activation and deactivation of business areas, types, status, queues and provide better visibility to usage in the database.  Once no objects exist in the database with those definitions, the configurations can be deleted.  Suggestions to improve OCU to improve reclassification of work is welcome.
3. Data administration must be improved to support deprecation of fields and visibility to the current usage on objects and business entity or business intelligence mapping.  Once no objects exist in the database with those fields, the configurations can be deleted.  Suggestions regarding how to improve visibility of data element usage and a related purge is welcome.