Example: A new hire’s identity is removed during a Workday aggregation that occurs the day before the new hire starts. When the next Workday aggregation occurs, the identity is added once more.
This behavior is caused by a mismatch between the Workday connector’s Effective Time Zone configuration value within Identity Security Cloud and the timezone in which the HR data (Hire, Termination, Re-hire, and Conversion) is processed.
Within Identity Security Cloud, the Workday connector's Effective Time Zone must be set to the same timezone in which the HR data (Hire, Termination, Re-hire, and Conversion) is processed.
For example, if the HR data is processed in the Central timezone, then the Effective Time Zone field (on the Connection Settings page) must be set to America/Chicago.
All valid time-zones are supported for the Effective Time Zone field. The following are some of the examples:
America/New_York
America/Los_Angeles
America/Chicago
PST
HST
Asia/Dubai
CET
GMT
ACT
Australia/Melbourne
Note
If the Effective Time Zone field is left blank, the timezone defaults to UTC.
Resolution:
-
Go to Admin > Connections > Sources.
-
Open your Workday connector.
-
On the Connection Settings page, locate the Effective Time Zone field.
-
Set the Effective Time Zone value to the timezone in which the HR data is processed.
-
Save the change.