000038680 - Owner approvals are skipped if the owner previously approved at least one item in the request as a supervisor in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Apr 3, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000038680
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
 
IssueChange request approval workflows may be configured for both supervisor approvals and owner approvals. Examples of owners are role owners, business owners, and technical owners. When an owner is also a supervisor and approves an item in a change request, the owner approval is skipped. This is true even when there are users in the change request that are supervised by someone else.
 
Cause This is the expected functionality of the product.
 
ResolutionWhen an owner is also a supervisor and approves an item in a change request, the owner is considered a previous approver so the approval is skipped. The previous approvers functionality has one function, it finds all approvers that have acted on the change request and if they are on the list, they are removed from having to approve again.
 
WorkaroundOptions to modify this behavior:


Previous Approvers



Remove the Previous Approvers option from the approval node of the approval workflow.


  1. In the user interface go to Requests > Workflows > Approvals tab > {workflow name}
  2. Click on the Approval node
  3. In the Activity Node Properties panel on the right-hand side under RESOURCES, remove the Dynamic: Previous Approvers setting using the trash can that appears when you click on this option.

 


User-added image

 

User-added image



Request Grouping



Modify the Request Grouping setting to group changes by user.


  1. In the user interface go to Requests > Configuration > Submission tab > Edit Settings
  2. Choose Request Grouping: Changes by user
 

User-added image


 

Attachments

    Outcomes