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.
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.
Modify the application to use default workflows:
Restart the RSA Identity Governance & Lifecycle application (acm restart). Note the default OOTB workflows are back:
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.
In the following example, specific worfklows have been defined for the Aveksa Application:
After an RSA Identity Governance & Lifecycle Application restart (acm restart), the workflow definitions have been retained: