Owner approvals are skipped if the owner previously approved at least one item in the request as a supervisor in RSA Identity Governance & Lifecycle
Originally Published: 2020-04-03
Last Modified: 2023-10-06
Article Number
000049749
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
 
Issue
Change 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.
 
Resolution
When 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.
 
Workaround
Options 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

 

Related Articles

Trending Articles

Don't see what you're looking for?