Runtime user availability and lifecycle

You can create and maintain users as needed for your specific environment. However, before users can take part in runtime operations, they must be available in the Business Automation Workflow database.

User activation

A user can be activated in the Business Automation Workflow database only if the user is available in a user registry. Users are activated through runtime operations, for example:
  • A user logs in to the product.
  • The user or users REST API resource is called with the refreshUser parameter.

You can also use these options to activate deactivated users. Generally, users are also activated when a user refers to another user for the first time through one of the runtime APIs.

User deactivation

Assignments and invitations through API calls
When you reassign a task to a deactivated user, the action is denied and you receive an error message. You can reassign the task to a different user, or restore the availability of the user you want to work with.

To handle deactivated users in clients, the user detail objects that are returned by REST and JavaScript API methods include a user availability status flag. In addition, the existing REST API method for looking up users allows you to restrict the result to only active or deactivated users. To identify deactivated users, you can use available methods to search for tasks that are possibly assigned to the deactivated users and decide on their reassignment.