Saviynt for Saviynt enableAccount does not show up in user's update history and trigger rules

[JustSalva]

Hi all,

We configured the Saviynt for Saviynt ENABLEACCOUNTJSON and DISABLEACCOUNTJSON to enable or disable saviynt users and exploit an actionable report to do so due to client's requirements.

{"EnableAccountQry":["update users set statuskey= 1 ,updatedate = utc_timestamp() where userkey = ${user.id}"]}

{"DisableAccountQry":["update users set statuskey= 0, updatedate = utc_timestamp() where userkey = ${user.id}"]}

We have two problems:

1. The tasks are performed correctly but the changes applied are not logged in the user update history, even though the status change is actually applied
2. User update rules are not triggered by the action, 

Can you suggest a resolution for both issues?

Kind regards,

Matteo

[sahajranajee · Accepted solution]

Hi @JustSalva ,

1. The tasks are performed correctly but the changes applied are not logged in the user update history, even though the status change is actually applied
   --> Since the users table is updated on the database directy, the changes are not recorded on the user update history. User History is only updated if the user is updated via UI,Import or API.
2. User update rules are not triggered by the action, 
   --> The same logic applies here as above. User Update rules are triggered only when a user is updated via UI,Import or API.

So if you setup a User Create/Update Form and submit a request for user updation, then you will be able to see the user update history and run rules from it, provided rules are set to 'Trigger when user is updated from UI' .

Or

You can build a SaviyntForSaviynt REST connector integration using Saviynt's APIs. Example :

and update user's status using the above api. This will also register is the user's history. And rules will be evaluated provided your rule is set to 'Trigger when user is updated from API' .

[JustSalva]

Hi Sahaj, 

thank you for your reply. The second option seems the one more in line with our requirements, but to trigger ENABLEACCOUNTJSON and DISABLEACCOUNTJSON from an actionable report would't we need to first import all saviynt users as accounts? Actionable reports require the accountkey to trigger those actions

[sahajranajee]

Hi @JustSalva ,

Yes, you can have the SaviyntForSaviynt DB connector as the Recon Connection and import users as account in the SaviyntForSaviynt endpoint. Then use the REST connector as the provisioning connection.

[JustSalva]

perfect, I'll try, thank you!