Workday ATS

https //www charthop com/pricing/ basic basic | | standard standard | premium available as an add on along with payroll data, the workday app also features its own ats that syncs open jobs data between charthop and workday workday ats default field mappings 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 workday ats additional field mappings the workday ats app supports additional field mappings for the following fields, which are known as operations in workday operation name description https //community workday com/sites/default/files/file hosting/productionapi/staffing/v33 2/get positions html#position restrictiontype 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 https //community workday com/sites/default/files/file hosting/productionapi/staffing/v33 2/get organizations html#supervisory org datatype 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 requirements for additional field mapping 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