No ratings
Saviynt Employee
Saviynt Employee

Use Case

Saviynt create and update user APIs are used to create/update user identities in Saviynt. This means there will large number of API calls as there can be large number of user records and for every record there will be an API call.

Moreover there can also be multiple sources from where Saviynt is receiving updates from different feeders via API Calls of different volumes at different time intervals. 




Basic Knowledge on the processRules API - This API allows the Saviynt Admin to run rules for unprocessed data in userrulerundata table manually
 "jobidstoprocess" : "0",   /**mention the parentjobid to run unprocessed rulerun for importjobentries**/
"runzerodayrules" : "true",  /** param to runzerodaytechrules **/
"totaljobstorun" : "2",        /** Mention the number of threads of rulerun job to be created **/
"batchidentifier" : "testbatch1"  /** batchidentifier for processing **/

jobidstoprocess - Should be 0 for processing webservice related entries in the userrulerundata table. Should be the parent jobid for processing the User Import related entries in the userrulerundata tablebatchidentifier - This is not a mandatory parameter. If we are using batch identifier in the createuser and updateuser API only then, it will make sense to use it in the processrules API.totaljobstorun - This count should not increase the maximum count of rulerunjobcount in the

Applicable Version(s)



For every API call, Saviynt will try to evaluate all the rules configured in the solution. Since there can be large number of API call, even a small delay in each call can add up to cause overall performance issue.

To avoid evaluation of rules add the parameter inlineruleevaluation=false in the Create User and Update User API call

Once all the new/updates for user record are completed from the external system calling Saviynt API and the Rule Run Entries for each user is being added into the userrulerundatatable. Then invoke /api/processrules API - this will trigger the rule evaluation for the users.

So we are creating and updating users via API with inlineruleevaluation=false. The Rule Run Entries for each user is being added into the userrulerundatatable. Finally once the Feeder has dumped all the data, /api/processrules API, is called to run the rules for the users. 

In case you have multiple sources/feeders sending API request at different timeslots and managing the /api/processrules is difficult as every feeder calls this api at the end; then in that case make use of batchidentifier parameter in createUser API and updateUser API. 

The External application will call the createUser and updateUser API with inlineruleevaluation=false and sets this wsbatchidentifier  for each and every create User and update User call
This value will be persisted against a column wsbatchidentifier in the userrulerundata table directly.
For example:

CreateUser API:


Update User API:


The rule run table will store the batch identifier information passed in the API. Refer below example

Userrulerundata table:


Now pass the batch identifier information in the ProcessRule API as follows:




Summary -

After making all the updates through create/update API, the External application should run the rules by calling /api/processrules API, with the same batchidentifier, so that only for the entries with this batchidentifier in the userrulerundata table will be picked up by the Rule Run jobs for Rule Evaluation .

  • In case of bulk user create/update using API, use the option inlineruleevaluation=false to improve API performance
  • Call the processrules API to evaluate the rules
  • In case you want to restrict processrules API to only certain users, then make use of batchidentifier parameter so that the change will be added into userrulerundata table populating the wsbatchidentifier parameter
  • Now, when the processRules API is called, mention the batchidentifier parameter in the API call to process only the selected entries.


Regular Contributor
Regular Contributor


Thank you for publishing this article. Very useful.

There is however contradicting statements between the article and the API documentation:

The article states :

  • In case of bulk user create/update using API, use the option inlineruleevaluation=true to improve API performance.
  • To avoid evaluation of rules add the parameter inlineruleevaluation=true in the Create User and Update User API call.

The API documentation for both /createUser and /updateUser states: "It's highly recommended to pass inlineruleevaluation:"false" for bulk load and call processrules api to evaluate and run the rules after the load is done."

The example API payloads show inlineruleevaluation as "false".

Please advise.

Saviynt Employee
Saviynt Employee

Hi @Paul_Meyer 


Thanks for notifying it. Yes it should be false and i have corrected it as well.





Version history
Last update:
‎06/26/2023 01:57 AM
Updated by: