Workday "TerminationDate" Attribute
Nov 28, 2025
Okta Integration Network
Okta Classic Engine
Okta Identity Engine
Overview
Applies To
- Workday app
- Attribute
- Okta Classic Engine
- Okta Identity Engine (OIE)
Cause
- If the termination date is set in the past within Workday, the user is deactivated before the attribute update reaches Okta.
- When the termination date is set in the future, Workday does not return the attribute in the API response to Okta. This omission can lead to Okta not being aware of impending terminations.
- Workday only allows access to the termination date attribute via API when it is set to the current date. This means Okta can only access and update the termination date attribute when the termination is effective immediately.
- One potential solution to address these issues is to map the termination date attribute to another field. However, this approach depends on Workday's support and whether such mappings are supported.
Solution
- Ensure that termination dates in Workday are accurately set and aligned with the organization's policies. Avoid setting termination dates in the past unless intended.
- Whenever possible, set termination dates to the current date in Workday to enable real-time synchronization with Okta. This ensures that Okta is promptly aware of it.
- Whenever possible, set the termination dates in Workday to the current date. This ensures that Okta stays in the loop in real-time and keeps access up-to-date.
- Pay attention to when imports occur in Okta. Ensure the import occurs after the terminate date attribute was sent in Okta, to capture the updated attribute.
