Esko Logo Back to Esko Support
Choose your language for a machine translation:
Skip to end of metadata
Go to start of metadata

 

Summary

This article explains what is the procedure involved when an admin user tries to delete a user having dependencies.

Symptoms

When trying to remove a user from WebCenter, the admin user confirms the deletion and is presented with a Delete Dependency Confirmation page.

Solution

The dependency page is used as a reminder that the user about to be deleted has outstanding dependencies such as being a task owner or an approver in an approval setup. At this point, the deletion can be cancelled if desired. 

If the administrator wants to proceed with the deletion, the Show Dependencies button should be clicked to show the user's current dependencies. This information may take a while to load.

The administrator may decide to remove the dependencies by re-assigning the tasks or approval setups. This should be done before deleting the user as it is much harder to find these assignments after the deletion of the user.

If the admin user is sure that the deletion of the user should proceed, then the Delete User button should be clicked. If there are still tasks assigned to this user (so the administrator decided to not remove this dependency), the task will become unassigned. Equally so, the user will be taken out of the approval cycle.

Article information
Applies to

WebCenter all versions

Created5-Nov-13
Last revised5-Nov-13
AuthorGEMU
CW Number178565
Contents