How to change a name of the change requests in RSA Identity Governance and Lifecycle
Originally Published: 2017-07-30
Last Modified: 2023-09-24
Article Number
Applies To
RSA Version/Condition: 7.x
Issue
For example, a request generated explicitly to add an entitlement to a user, request will be generated as:
On the other hand, when a request is generated through a review (Any type of a Review) , its name is set with the same name as the review Result.
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 requests 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.
This article discusses possible ways to change the name of requests generated explicitly, and through Roles and Reviews.
Resolution
In 7.x, to view and change Prefix Settings, go to a Requests --> Workflows --> 'Request' tab. Click on the 'Delegation Only' workflow.
(1) Use Object Name For Prefix — Select if you want the name of the user for whom the change request is generated use 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-00022.”
This will generate a request, for example, through a Role, as follows:
You can configure either the “Use Object Name for Prefix” option or the “Prefix” option, but not both.
To add a unique identifier to a request name generated through a review, one possible 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 a Request Name (or replace that name with Unique ID, etc).
To perform this customization, you may engage RSA Professional Services team who can assist you to customize the default workflows to change the request names to ones that are suitable to your business needs.
