- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Split a Change Request into Separate Requests
Hello,
Is there a system, application or workflow setting that would force requests from a specific source (such as roles) to be split into unique requests by person?
If the request generates an error it causes cascading failures for the remaining changes in sequence after it, leaving us with manual fulfillment for multiple items instead of only the one that caused the error.
We have tried using the workflow setting "create an individual job for each change", however that has not made a difference for this scenario.
Thank you.
- Tags:
- Access & Change Requests
- Community Thread
- Discussion
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- IG&L
- IGL
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
At the moment they cannot be split, however since these are not "Role Changes” but more of "User Changes” technically it should be possible. I would suggest logging an enhancement request on RSA Ideas for RSA Identity Governance & Lifecycle. Also check out How to make your RSA Idea stand out!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
No one replied to your question, just replying to make the post current and see if anyone has any suggestions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
You can do that for explicit change requests from Requests > Configuration > Submission > Request Grouping > Changes by user. You can also control this on the Request Form level.
You can also control this in Reviews by changing the change request generation to "Explicit by Owner”. Take a look at RSA IGL Recipes: Scheduling Review Change Request Generation using Web Services for more details
However Role requests (that are generated from Committing role changes) are the only ones that cannot be split. A Role change can only be generated and processed as a whole.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
This is important to note. Thanks Mostafa Helmy
However Role requests (that are generated from Committing role changes) are the only ones that cannot be split. A Role change can only be generated and processed as a whole.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Thank you both for your responses. For my clarification - are requests created from role UINC and UOOC rules included with the the role requests that cannot be split?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Correct Role changes cannot be split.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
At the moment they cannot be split, however since these are not "Role Changes” but more of "User Changes” technically it should be possible. I would suggest logging an enhancement request on RSA Ideas for RSA Identity Governance & Lifecycle. Also check out How to make your RSA Idea stand out!
