Workday ATS
Along with payroll data, the Workday app also features its own ATS that syncs open jobs data between ChartHop and Workday.
The Workday ATS app supports the following default field mappings listed in the table below:
ChartHop field label | Workday field code |
Workday Req ID and Req | wd:Position_Data.wd:Position_Definition_Data.wd:Position_ID |
Title | wd:Position_Data.wd:Position_Definition_Data.wd:Job_Posting_Title |
Department | wd:Organization_Data.wd:Name |
Location | wd:Organization_Data.wd:Supervisory_Data.wd:Location_Reference.wd:ID |
Manager and Hiring Manager | wd:Organization_Data.wd:Manager_Reference.wd:ID |
The Workday ATS app supports additional field mappings for the following fields, which are known as Operations in Workday:
Operation name | Description |
Returns information for position management positions. If a position is filled, it identifies the worker filling the position. This operation is specified via wd:Position_Data in the field mappers. | |
Returns organization information for a type of organization. If the request does not specify an organization, the operation returns information for all organizations. This operation is specified via wd:Organization_Data in the field mappers. |
When mapping additional Workday fields, you need to consider the type of field you are mapping. Most Workday fields are stored as objects and need additional formatting when creating the mappings. To reference the path for additional mappings, for each parameter that is an object type, you need to specify the nested end parameter within the object:
Example path - wd:Position_Data.wd:Position_Definition_Data.wd:Job_Posting_Title
Using the above example, to pull Title, you would start with Position_Data (as this is under the Staffing/Get_Position operation), followed by Position_Definition_Data and ending with Job_Posting_Title. This final parameter (Job_Posting_Title) is a string and is pulled in as the field value.
Note that when creating a nested path, you must add wd before the first parameter in the path, followed by a .wd for each additional parameter in the nested path.
