04/21/2023 12:07 PM
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?
Solved! Go to Solution.
04/21/2023 12:11 PM
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
04/21/2023 12:31 PM - edited 04/21/2023 12:32 PM
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.
04/21/2023 01:07 PM
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
04/23/2023 04:39 PM
Can you share sample input file
04/25/2023 05:35 AM
USERNAME,STATUSKEY,TERMDATE,CUSTOMPROPERTY60
001234,0,2023-04-25,TERMINATED
05/02/2023 07:33 AM
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