Introduction
This guide explains how to manage UKG Pro ATS jobs using Kombo's platform, addressing the challenge of differing support for job locations between UKG and our V1 data model.
Problem Statement
Our V1 data model does not support multiple job locations for a single job, whereas UKG Pro ATS does. This difference requires a specific approach to ensure accurate job representation and application tracking.
Solution
To handle this, we create a separate job entry for each UKG job location in our data model. Additionally, we have a base job entry without a location to help with application tracking.
- Base Job: This job has a unique remote ID, such as
048567a4-5e2c-4a08-aaec-41daeebfab8e, and does NOT include a location and will return "location": null. - Location-Specific Jobs: These jobs use the same base remote ID, followed by a location ID, separated by a colon. For example,
048567a4-5e2c-4a08-aaec-41daeebfab8e:1642d5f8-2aa3-5a84-ab94-2c370062df9b.
Application Tracking
UKG's API does not specify which applications belong to which job location. Therefore, all applications are tracked under the base job entry. This method ensures all applications are managed effectively.
Recommendations
- Showing Jobs to Candidates: When displaying jobs to candidates, show only those with location information. This makes the job search clearer and more relevant for candidates and avoids duplicate job entries.
- Managing Applications: Remember that applications are linked only to base job entries (without location). This simplifies accessing and managing application data.
By following these guidelines, you can effectively manage UKG Pro ATS jobs within Kombo, ensuring a smooth process for job postings and application tracking.