How can we force users to select only one entitlement at a time in Entitlement Tables embedded in Request Forms? Below is our current configuration but with this one, users are able to select more than one entitlements at the same time.
OK few things here .
When ChangeItemHandling is set to Subject may have one entitlement, that means it will remove others , as we explicitly wants user to have only one.
Now I got your problem , and then I saw for Entitltment Table we have an option "Select only one Entitlement" for all Change Item Handling.
So You can select go ahead and select Change Item Handling as "Add Selected Items " and also select "Select only one Entitlement" .
This might help with your use case here.
You donot have an option with Entitlement Table with Action, But you do have an option with Entitlement Table .
In Entitlement Table you can select ChangeItemHandling as Subject may have one entitlement.
Thanks Nilesh Jain,
We tried with Entitlement Table and saw the option that you referred. However, I see one problematic behavior in the following scenario;
Suppose there 2 users that we want to add a new entitlement (in this case, the entitlement is business-role). Also suppose that one of the users has already been assigned to a role previously.
1- If we select users in the User Selection Form an hit next, in the entitlement table we see that first line is highlighted and indicating the fact that some of the target users are assigned to a role listed.
2- Then, we select another business-role to which neither of these 2 users are assigned.
3- In the request created, user is removed from the role he is already assigned and 2 users are assigned to the selected role. (Picture 2)
But we should not lose the role that the user is currently holding. Is this a bug?
How can we prevent this problematic behavior?
Is there are way to organize request form such that it first displayed the roles to be added and then the users? This way we could eliminate the risk for losing already existing roles.
Retrieving data ...