Admin - AlexB.73752 (Customer) asked a question.
Hello,
We are having an issues with Workday profile masted users. When a user is either backdated or immediately terminated certain attributes are not being written to the users profile that we would like to be there. The user becomes suspended in Okta but we would also like the following attributes to be updated. customLifecycleState, customTerminationType and customTerminationDate. We have these attributes mapped in Okta and are set to create and update. The Workday applications stays assigned to the users profile when suspended as well. I have tried running incremental and full imports after the user is suspended but the attributes are not updated. I can see the attributes are updated in Workday and the ISU I am using in Okta can see the suspended users in Workday.
We are using RTS for termination reasons as well.
Any ideas what can be causing this?
Hello @Admin - AlexB.73752 (Customer) , thank you for contacting Okta Community.
During an import, the membership phase processes are run before the user attribute update phase. Once the account is detected as inactive, the AppUser is considered unassigned, so subsequent updates do not make changes. You can read more about it here:
User Attribute Not Populating from Profile Source Application
You need to ensure the attribute updates occur prior to the AppUser import marking the profile as inactive.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
This month's AMA topic: Okta Device Access. Ask away today.