In RSA Identity Governance & Lifecycle, an application restart resets the Aveksa Application request workflows to OOTB if using default workflows
Originally Published: 2019-07-23
Last Modified: 2023-10-06
Article Number
000054772
Applies To
RSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.x
 
Issue
In RSA Identity Governance & Lifecycle, an application restart resets the Aveksa Application request workflows to the Out-of-the-box (OOTB) workflows if (Use default) is selected for the workflow definitions.

The following example explains this in more detail.
  1. In the RSA Identity Governance & Lifecycle user interface, go to Resources >  Applications > Aveksa > Requests tab and scroll down to the Approval and Fulfillment sections. Note the default OOTB approval workflow is Asset Business Owner Approval and the default OOTB Fulfillment workflow is Security Fulfillment Handler.
User-added image
 
  1. Modify the application to use default workflows:
User-added image
  1. Restart the RSA Identity Governance & Lifecycle application (acm restart). Note the default OOTB workflows are back:
User-added image


 
Resolution
This is expected behavior. For the Aveksa Application, the approval and fulfillment workflows must be explicitly defined in the Application configuration in order to be retained between application restarts. This is not true for user-defined RSA Identity Governance & Lifecycle applications. This is specific to the RSA Identity Governance & Lifecycle Aveksa Application.
 
  1. In the following example, specific worfklows have been defined for the Aveksa Application:
User-added image
 
  1. After an RSA Identity Governance & Lifecycle Application restart (acm restart), the workflow definitions have been retained:
User-added image
Don't see what you're looking for?