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

User Modification Workflow is triggered even when updating user from Identity Repository User Page

yogesh
Regular Contributor III
Regular Contributor III

We have added a "User Modification Workflow" in Identity lifecycle, it is triggered when a user is created/updated via User Create / Update forms. But this workflow is being triggered even when updating users from Admin Screens i.e. Identity repository > Users .

Is there a way to bypass the workflow when updating user from their profile page, such updates should not create any requests and if requests can not be prevented at least have those auto approved?

4 REPLIES 4

rushikeshvartak
All-Star
All-Star

There is no difference in request created from admin or via Request Tile. Hence you won't be able to bypass workflow


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

sahajranajee
Saviynt Employee
Saviynt Employee

Hello,

Both the ways to update users will use the same 'User Modification Workflow'. If you want separate flows for both, i would recommend creating a dynamic attribute for the Create/Update User Request form which populates a default value on some user property when updated from there and accordingly make it auto approved. 

See below :

sahajranajee_0-1654666721700.png

 




Regards,
Sahaj Ranajee
Sr. Product Specialist

yogesh
Regular Contributor III
Regular Contributor III

@sahajranajee @rushikeshvartak 
After migrating the workflow and the form to our TEST environment we noticed that workflow is not getting triggered anymore when updating user attributes from user profile.

So we enabled the workflow in DEV to check, and to our surprise it is not getting triggered in DEV as well when updating user attributes directly from their profile page.

Do you have idea what may cause this change in behavior? It is working as per our expectations now but we don't know what 'fixed' it, and we thus have concerns if it might break in future unexpectedly. The workflow has not been updated.

rushikeshvartak
All-Star
All-Star

Just change name of ifelse block & reimport & check in versions tab under workflow


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