- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Entitlements Held By users Should Display At The Top
Hi,
Suppose in a scenario , Any particular application is heaving 10000 entitlements( Ent1 to Ent10000 ). Those entitlements we are displaying on the entitlement request form using the below configuration.
my question is , when user A is accessing the entitlement request form and selecting ent1 from page 1,ent50 from page 50 ,ent1000 from page 1000. how can we display "ent1,ent50,ent1000" at the top of the page of entitlements table before submission?
after selection of ent1,ent50,ent1000 should display at the top . other wise ,if anybody wants to review the selection before submission he must have to go again page no 1,page no 50 ,page no 1000 which is a time taking job.Kindly help.
- Tags:
- Community Thread
- Discussion
- entitlement filter
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- IG&L
- IGL
- Request Forms
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
- select entitlement logic
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I don't think there is an out of the box way to order entitlements based on whether the affected users has them or not.
I understand why you want to have this option, so I would suggest logging an idea under RSA Ideas for RSA Identity Governance & Lifecycle (Ref: How to make your RSA Idea stand out!).
On the other hand, I don't think having 1000+ entitlements/pages on a single form for users to pick from is a business friendly idea. You might want to reconsider your form design to make it more business friendly. For example, split them by application/functionality … etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Rajkiran,
Sorry, but I'm not sure I understand the use case fully. If User A already has Ent1, Ent2, Ent3 and Ent4 why would these need to be included as part of the submitted request again?
Thanks,
Clive
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hello Clive,
Sorry for the misunderstanding. I rectified the query.
my question is , when user A is accessing the entitlement request form and selecting ent1 from page 1,ent50 from page 50 ,ent1000 from page 1000. how can we display "ent1,ent50,ent1000" at the top of the page of entitlements table before submission.After selection of ent1,ent50,ent1000, selected entitlements should display at the top . other wise ,if anybody wants to review the selection before submission he must have to go again page no 1,page no 50 ,page no 1000 .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I don't think there is an out of the box way to order entitlements based on whether the affected users has them or not.
I understand why you want to have this option, so I would suggest logging an idea under RSA Ideas for RSA Identity Governance & Lifecycle (Ref: How to make your RSA Idea stand out!).
On the other hand, I don't think having 1000+ entitlements/pages on a single form for users to pick from is a business friendly idea. You might want to reconsider your form design to make it more business friendly. For example, split them by application/functionality … etc.
