Table to object schema mapping

Each table that supports data replication has a matching object schema. The schema file name is prefixed with "WFM_" and uses the camel case of the WFM table name. For example, the WORK_DETAIL table has a matching WFM_WorkDetail object schema.

Each column in a table is mapped to one field in an object schema. Field names use the camel case format of the column name. For example, the WRKD_START_TIME column is mapped to the wrkdStartTime field.

Each column is mapped to the appropriate JSON data type. Additional attributes such as minimum, maximum, and multipleOf are provided in the object schema where appropriate.

All columns in the table are included in the object schema (except the legacy CLIENT_ID column, which is no longer used). Fields in the object schema have the same order as what is in the table.

Workforce Management stores the local time for most DATE and TIMESTAMP columns. Since these are not in UTC, they are mapped to a String in the object schema. Date only values are formatted as yyyy-MM-dd. Time only values are formatted as hh:mi:ss. Datetime values are formatted as yyyy-MM-dd hh:mi:ss. Timestamp values are formatted as yyyy-MM-dd hh:mi:ss.sss.

Any DATE or TIMESTAMP columns in Workforce Management that have a UTC value have UTC in the field name. These are mapped to date-time in the object schema.

Depending on the type of value stored in the DATE or TIMESTAMP column (date-time, date only, time only), additional Date, Time, and UTC datetime fields may be provided. For datetime values that are related to an employee, the employee’s timezone is used to calculate a UTC datetime value.

Note: Any employees assigned to the default time zone (None) should be updated to their actual time zone based on their location before the Data Replication task is enabled.

For datetime columns that are related to the system, the system time zone is used to calculate the UTC datetime value.