Article Number
000038624
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1, 7.2.0
Issue
When the Cancel Change Request workflow node is defined with the Event Type
Move requests to error state option, the change request moves to an Error state but remains in an ACTIVE state. Because the change request is in an Error state, there is no way to cancel or progress the request, thus the ACTIVE state is permanent.
In the example below, request 00012 is in a partial error state, is not cancelable and remains ACTIVE.
Requests > Requests
Image descriptionRequests >
Requests > {
Request name}
Image descriptionRequests >
Requests > {
Request name} >
Processing Workflow
Image description
Cause
This issue occurs when the Cancel Change Request workflow node is configured with the Event Type set to
Move requests to error state and when there are no comments in the Notes field as illustrated in the example below.
Requests > Workflows > {relevant tab} > {name of workflow} > Cancel Change Request node > right-hand side under Definition.
Image description
This is a known defect reported in engineering tickets ACM-103239 and ACM-103387.
Resolution
This issue is resolved in the following RSA Identity Governance & Lifecycle patches:
- RSA Identity Governance & Lifecycle 7.1.1 P06
- RSA Identity Governance & Lifecycle 7.2.0 P01
Workaround
The workaround is to add a comment to the Notes field when saving the workflow. For example,
Requests > Workflows > {relevant tab} > {name of workflow} > Cancel Change Request node > right-hand side under Definition.
Image description
Once the node is configured with a comment in the Notes field, the behavior is as expected and the change request goes into a full ERROR state.
Requests > Requests > {Request name}
Image descriptionRequests >
Requests > {
Request name} >
Processing Workflow
Image description