|Applies To||RSA Product Set: RSA Identity Governance & Lifecycle|
RSA Version/Condition: 7.1.0
|Issue||RSA Identity Governance & Lifecycle Access Fulfillment Express (AFX) Change Requests that have Entitlements Require Account enabled show that the Create Account activity is in a Completed state, but the dependent items such as the Add Account to Group remain stuck in the Waiting On Dependencies state. |
The workflow shows that the dependent items are in the Calculate Items To Work On node which is in an Active state:
|Cause||This issue only affects AFX fulfillment workflows that contain the Java node Calculate Items To Work On. This issue does not affect the Default AFX Fulfillment workflow shipped with RSA Identity Governance & Lifecycle 7.1.0 or workflows based on the 7.1 version of this workflow. This issue does affect workflows created on an earlier version of RSA Identity Governance & Lifecycle, or based on an earlier version of the Default AFX Fulfillment workflow.|
This problem is caused by the Alert on the Calculate Items to Work On node being incorrectly assigned to the wrong WorkPoint Alert queue.
|Resolution||This issue is resolved in RSA Identity Governance & Lifecycle 7.1.0 P02 which includes an updated workflow migration utility script that runs during the application of the patch that modifies problem workflows to correct the issue.|
|Workaround||For workflows on RSA Identity Governance & Lifecycle 7.1.0 GA or RSA Identity Governance & Lifecycle 7.1.0 P01 that exhibit this problem, the migration script ACM-88269.sql may be run manually as a repair script on affected systems under the guidance of RSA Customer Support to correct any problem workflows. |
Please contact RSA Customer Support for a copy of this script and guidance on how to use it.
This issue only occurs if the Workflow is configured with the Select the grouping of changes set to either:
This issue affects workflows that are exported and imported as metadata from one instance of RSA Identity Governance & Lifecycle 7.1.0 to another. In environments where customers are exporting workflows from one instance and importing into another, customers should ensure that all environments are patched or that the repair script is run on all instances to avoid reintroducing workflows that have this issue into new machines.