Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Application Collection only valid if user does not have an account?

New Contributor
New Contributor

Noticed something with application collections.  If you want to build one it seems to require you to add a new account.  If you already have an existing account, you can't build an application collection from the modify access screen.  If the user that requests an application collection already has an account, it will show the account name as the account for the person that built the application collection (looks like a bug), but when it goes to provision if the user has an account, it will try to create a new account for that user.  If you have the flag turned on the endpoint to disable new account when user has existing one, it will error on the shopping cart request when you try to submit.  
Is this the desired use case for an application collection?  Should it only be used for new users that do not have an account already, vs using it to bundle entitlements that are not managed via an enterprise role?




Please raise defect in freshline to support team

Rushikesh Vartak
If you find this response useful, kindly consider selecting 'Accept As Solution' and clicking on the 'Kudos' button.