How to change a request name generated though reviews in RSA Identity Governance and Lifecycle?
Originally Published: 2017-07-07
Article Number
Applies To
RSA Version/Condition: 7.x
Issue
For example:
You have created a User Access Type review named "User Access Review" and ran it. This generates the Review Result named "User Access Review-1" by default.
If a change request is created to revoke an entitlement for a user within this review, then the request created has a name "User Access Review-1".
Multiple requested created will use the same name "User Access Review-1"
This makes it hard to distinguish all the requests created within a review result.
Using a workflow with the object name does not help. It works only for explicit requests.
Is there an out-of-box functionality to generate each request with a unique name when it is created though a review?
Workaround
Below are two settings that are used in a Request Workflow. Go to a Request Workflow, and click 'Edit'. For Example:
In 7.0.1
(1) Use Object Name For Prefix — Select if you want the name of the user for whom the change request is generated used a prefix in the system-generated change request identifier. For example, if a request is generated for user “John Smith,” then the change request identifier would appear similar to the following: “John Smith-00017.”
(2) Prefix — Specify a prefix for the system generated change request identifier. For example, if you specify the prefix, “Role Access Request,” the request identifier would appear similar to the following: “Role Access Request-00017.”
You can configure either the “Use Object Name for Prefix” option or the “Prefix” option, but not both.
To add a unique identifier to be added to each CR created within a review, in review name, best option is to add a SQL node to a workflow and generate the sequence number or a Unique ID via that SQL Node and append that to the CR name created by a Review (or replace that name with Unique ID etc)
Related Articles
Change Request generated by Role Review shows as Rejected in RSA Identity Governance & Lifecycle 30Number of Views RSA WebSerivce "Invalid column name" when creating a change request to terminate a user in RSA Governance & Lifecycle 13Number of Views If the FSM user services are stopped (accidentally/deliberately) will the system administrator be able to access the file… 5Number of Views An empty change request is created when attempting to commit a role using the "Actions" button, even though no changes or … 22Number of Views How to change the explicit Change Request (CR) name to include the CR details in name section in RSA Identity Governance a… 86Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?