Review escalation workflows do not trigger if review is set to Hold by an escalation workflow after due date in RSA Identity Governance & Lifecycle
Originally Published: 2020-09-22
Article Number
Applies To
RSA Version/Condition: 7.1.1, 7.2.0, 7.2.1
Issue
For example,
1. Make a copy of the default "On Hold Review" workflow but with the Review Status changed to Complete.
2. Edit the default user review to set the due date as 1 day.
3. To a default user review associate the escalations to change the review state to hold after 1 day and then change the state to complete after 2 days.
4. Run the review
5. You will see the OnHold escalation triggers but the next escalation does not get triggered.
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P11
- RSA Identity Governance & Lifecycle 7.2.0 P05
- RSA Identity Governance & Lifecycle 7.2.1 P01
Related Articles
Notification rule triggers daily for the same admin error in RSA Governance & Lifecycle 19Number of Views Workflow Decision Node takes wrong path in SecurID Governance & Lifecycle 76Number of Views RSA Governance & Lifecycle 7.5.2 Release Notes 37Number of Views Users tab slow to load in SecurID Governance & Lifecycle 127Number of Views Performance Implications of database statistics computed on GTT* tables 55Number of Views
Trending Articles
How to generate a PASSCODE for manual entry on a Ericsson R380 WAP phone RSA Authentication Manager Upgrade Process How to Understand the Difference Between RSA Authentication Manager Licenses and SecurID Token Assignments How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 3.0 for Microsoft AD FS Administrator's Guide
Don't see what you're looking for?