I am seeing an issue with an application where I have made the entitlement selection mandatory during request. The issue is that when I remove all the entitlements from ARS and submit the request, I would expect Saviynt to throw an error as the mandatory entitlement selection is missing. But instead it just allows me to submit the request removing the access. Is this some kind of bug? Can someone please advise ?
@pruthvi_t . Thank you for the response. I have kept the 'Required-Standard' to 'true' in order to make the entitlement selection mandatory
Also, this behavior is not seen with other apps. The difference with this app is that, here I have one entitlement 'Default' which should not be visible to end users to request for addition or removal. and hence, I have added the entitlement query as below at the entitlementtype level to make sure user does not see this during request to either add or remove. (Note: This 'Default' entitlement could be added to user as part of import and hence I have also added it under 'Config for Selected Entitlement in ARS' also so that user cannot remove it from ARS )
Additionally, if I remove the 'Config for Selected Entitlement in ARS' query from the entitlementtype, then it works as expected and does not allow me to remove all entitlements and submit the request in ARS. But, if I don't have that query, then user can also see the 'Default' entitlement in ARS to remove it which we don't want