Click HERE to see how Saviynt Intelligence is transforming the industry. |
06/02/2022 02:12 AM
Hi There,
We need some urgent assistance from any tech expert here.
We are using saviynt 2020.1.2v for the prod instance. there is a required to update user's email address in workday using soap api. so we have update user payload created and working. But to trigger the update user task we have created a user update rule which has following conditions.
1. Trigger action when user is updated from import
2. Condition: (##a.email isupdated##) AND (a.email is not null) AND (a.statuskey=1) using advance query.
3. Tried without using advace query option with same conditions.
4. When above condition is met, set Action as Create update user task for workday connection where we have update user json present.
In our setup, user email gets updated by the ImportAD user job which is running fine and able to update user email attribute. So as per this we have setup the above user update rule and expected saviynt to create update user task. But it is not happening although job is updating email address for users.
There are no errors noticed in the debug logs. But we are unclear why saviynt unable to trigger update user task even the condition is met. The same logic we tested in our UAT where we have 2020.1v and it works there. Unfortunately we have version difference, So i am not sure if that is issue here.
Also the update user task is trigger with other update rule "we have set trigger when user updated from Ui".
Any help would be greatly appreciated.
Thanks
Sampath
Solved! Go to Solution.
06/02/2022 02:18 AM
Hello,
The rule config looks fine. Please check on the following :
1. The 'Trigger Actions when' is set to 'Trigger when user is updated from Import'
2. The connection linked with 'Update User' task is also associated to a Security System as Provisioning Connection.
06/02/2022 02:22 AM
Hi,
Yes, i have already selected same trigger action. And also selected security system as workday connection our update user json exist.
As i mentioned same thing works in UAT but not working in Prod. But we have version differences. UAT is 2020.1 and Prod is 2020.1.2
Thanks
Sampath
09/15/2022 01:03 AM
Hello Sampath.
Did you get a solution of it?
Regards,
-Vinit
09/15/2022 01:12 AM
Hi Vinit
Yes, i found the solution, there was a misconfiguration in the job we created. Forgot set the check rules condition to yes, so it resolved the issue.