000038624 - Cancel change request workflow node defined with the 'Move request to error state' option leaves the workflow in a permanent ACTIVE state in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Mar 24, 2020Last modified by RSA Customer Support Employee on Jul 30, 2020
Version 31Show Document
  • View in full screen mode

Article Content

Article Number000038624
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1, 7.2.0
 
IssueWhen 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

 

User-added image

Requests > Requests > {Request name}

 

User-added image

Requests > Requests > {Request name} > Processing Workflow

 

User-added image


 
CauseThis 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.

 

User-added image



This is a known defect reported in engineering tickets ACM-103239 and ACM-103387.
 
ResolutionThis 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
WorkaroundThe 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.

 

User-added image



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}

 

User-added image

Requests > Requests > {Request name} > Processing Workflow

 

User-added image


 

Attachments

    Outcomes