Please review instructions here to get started with setting up an Assets import configuration. You can then access OnLink app from the “Manage your apps” menu to further configure and set the field level mapping. Here’s an example configuration:
Here’s a sample mapping config:
key:employeeId=WorkerIDmap:firstName=Namemap:emailAddress=JiraUsermap:jobtitle=Titlemap:supervisorId=Managermap:originalHireDate=HireDateconfig:data_source=personnel/v1/employee-demographic-details
Here’s a breakdown of some of the mapping configuration items:
Key or Map | Description |
|---|---|
| The keyword “key” refers to using Worker_ID as a unique identifier. This allows OnLink to update the record. WorkerID is a text attribute. |
| Maps firstName to Name text attribute |
| The emailAddress field containing email address of worker is mapped to JiraUser, which is an attribute of type “User”. Here OnLink looks-up the Atlassian User object based on the email address. |
| Set to a valid API URL e.g. personnel/v1/employee-demographic-details Any API from this document can be included in this attribute: https://developer.ukg.com/hcm/reference |
OnLink processes data in two steps - Get Data and Import Data. To manually test, you can click on Get Data first and then wait until you see “No more pending records. Data will be imported on next Import run.” message in Job Logs. Then, click on Import. Production runs are fully automated based on the schedule you choose.
