Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
I’m looking to find out if anyone has come across the need to aggregate users from UKG’s Recruiting product. Our organization processes new hires and rehires through the UKG Recruiting gateway. They migrate from the Recruiting gateway to the Onboarding gateway and don’t make their way to the Pro Core product until the first, second, or even third day after the user is started. We need to process the Joiner lifecycle in advance of them starting. UKG supports different API capabilities for their different products but with drawbacks. The best option we have found so far is using their Reports-as-a-Service where we build a report in UKG containing Recruiting data and then retrieve the report via their RaaS web service. We are working to prove this out now, but looking to find out how others are aggregating new hires and rehires from UKG Recruiting ahead of their start date.
I have used a webservices connector to the reports-as-a-service endpoint to address this problem. In one case, we were able to get all of the new users in one report; in another case we had to use multiple reports and merge them with our rule logic.
That’s great to hear. Out of curiosity, did you have to create a web user account or could use their web service accounts? Documentation says web service accounts cannot read Recruiting data. Also, what use cases did you encounter that lead you to building multiple reports in case we are going to face the same thing?
I am not sure on the type of user - My understanding was that HR did their part of the setup and then had to create a ticket with UKG to get the user able to access the reports through the Reports-as-a-service interface.
I think the integration that had multiple reports had different columns that were important for pre-hires versus active employees, so it was easier to get the data. In the web services rule, we ran each report and then looped through the result sets to get to one cohesive set of users to aggregate.
We did this with a Web Services connector calling the Onboarding API directly instead of creating a report. We call the /new-hires/in-progress endpoint, although you may need to call the /new-hires/completed endpoint also if users are not loaded into Core until sever days after their hire date. You will need to request access to this API through UKG Support. The documentation for requesting this access and using this API can be found here, however you will need a UKG account to access the links. We had to have someone from our HR team with a UKG account send us copies of this documentation.
This onboarding connector is separate from our UKG Core connector with its own Identity Profile. The priority on our Core connector is set to a lower number and we correlate the accounts on the externalUserId field, which has the same identifier in both UKG Onboarding and Core for each user. Users can be aggregated/onboarded through the UKG Onboarding connector to get their accounts created and when the come through the UKG Core connector, the accounts get correlated and the identity gets promoted to a UKG Core identity. Eventually, the UKG Onboarding record drops off and the user just has their UKG Core account/identity.
Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.