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

Schema Upload Job is triggering Remove Account task instead of Disable Account

alanbixby
New Contributor III
New Contributor III

We are experiencing different behavior in our development and production environments when we go to run a Schema Upload job for Terminated_Users.sav:

#USER_NOT_IN_FILE_ACTION=NOACTION
#DELIMITER=,
#ZERODAYPROVISIONING=FALSE
#userReconcillationField=USERNAME
#GENERATESYSTEMUSERNAME=FALSE
#GENERATEEMAIL=FALSE
#CHECKRULES=TRUE
#SKIP_NUMBER_OF_LINES=1
#STATUSKEYJSON={"STATUS_ACTIVE":["1","Active"],"STATUS_INACTIVE":["0","inactive"]}
USERNAME,STATUSKEY,TERMDATE,CUSTOMPROPERTY60

Production creates a "Disable Account" task (intended), Development triggers a "Remove Account" task.

Setting the status key to Inactive manually will trigger a Disable Account task in both environments.

Where is this behavior for the Schema Upload job configured?

6 REPLIES 6

dgandhi
All-Star
All-Star

This depends on the rules that you have configured in your DEV and Prod environment.

Can you check if both the environment have same set of actions?

Thanks

Thanks,
Devang Gandhi
If this reply answered your question, please Accept As Solution and give Kudos to help others who may have a similar problem.

alanbixby
New Contributor III
New Contributor III

Could you elaborate on which rules we should be checking?

Comparing all of our active policies, the environments match for all technical rules, user update rules, etc. I also "validated" there were no minor typos/flipped flags by checking off each rule using CTRL-F in both directions.

Check the user update rule and technical rules of both the environment and also the action that you have setup for these rules.

Also I hope both DEV and Prod are on same version of the Saviynt instance just to rule out any environmental issues.

Thanks

Thanks,
Devang Gandhi
If this reply answered your question, please Accept As Solution and give Kudos to help others who may have a similar problem.

rushikeshvartak
All-Star
All-Star

Can you share sample input file


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

USERNAME,STATUSKEY,TERMDATE,CUSTOMPROPERTY60
001234,0,2023-04-25,TERMINATED

alanbixby
New Contributor III
New Contributor III

We have independently resolved this issue.

User Termination from Imports was set to Enabled in the development environment, clearing the value corrected the behavior.

Admin > Global Configuration > Identity Lifecycle > Offboarding > User Termination from Imports