Skip to main content

Workflow logic and process

The Workflow Manager Service is responsible for implementing authorization logic and orchestrating workflow processes. In general, the workflow process operates as follows:

  1. A user logs into the Bravura Security Fabric web application and submits a change request.

    Alternatively, an automated process may submit the change request.

  2. Bravura Security Fabric validates the input and forwards the request to the Workflow Manager Service (idwfm).

  3. The idwfm service determines authorizers for the request using static authorization or dynamic authorization rules, and notifies them of their assignments by email.

    Caution

    Assigning too many authorizers could affect performance. When the number of authorizers assigned to a resource exceeds the value of MAX AUTH ALLOWED (default 20), the request is put on hold. If you increase this value, ensure that you test the configuration for performance issues.

  4. Authorizers log in to the Bravura Security Fabric web application, usually after following a URL embedded in the email, where they log in and either approve or deny the request.

  5. If authorizers do not respond in a timely manner, idwfm can send reminder emails or take other actions like denying or escalating the request.

  6. The idwfm service determines if input received from authorizers is sufficient to approve or deny the request. If the request is:

    • Denied, idwfm closes the request.

    • Approved, idwfm forwards the request to the Transaction Monitor Service to carry out changes on target systems.

      The fulfillment engine can be configured to run connectors directly or to use human implementers.

    The idwfm service also updates the Bravura Security Fabric database and informs the appropriate users.

In this section: