Click on Assets and click on the schema you want to import data into. Then click on Schema configuration -> Import -> Create Import and then select OnLink Importer. Give the Import a name and click on Create Import.
Click on the three dots and select Configure app, then set a name in the Configure mapping attributes popup. Click on Save configuration.
Then click again on Configure app to get a link (“to edit config use this link apps“) to the app where rest of the mapping needs to be setup. Click on the link to go to the OnLink app configuration.
You should now see a configuration in OnLink. Select Edit in the drop down. Here you can select the Source system and rest of the configuration.
For Azure and Workday, ensure their connectivity settings are configured in OnLink - Connections tab
For Workday, select the Report name (username and report name combination e.g. “lmcniel/employee_data”).
Schema is pre-selected in OnLink and is lined to the schema you selected in step 1. Set object type to the specific object you want to map to. Then map field level attributes (source data field is on the left side and the object attribute appears on the right side). Use “map” prefix for field mapping and “key” prefix for a unique identifier that will be used to identify objects for update purposes.
map:First_Name=Firstname
map:Last_Name=Lastname
map:Title=Title
map:Email=Email
map:Manager=Manager
map:HireDate=HireDate
map:DepartmentRef=DepartmentRef|RefID=${DepartmentRef}
map:Location=Location
key:Worker_ID=WorkerID
To map references to other schema attributes, you can specify AQL after the pipe symbol as shown above for mapping DepartmentRef. DepartmentRefID is the value coming from Workday custom report. DepartmentRef is the attribute in schema pointing to Department object. RefID is the attribute on Department object. Here’s an example object definition - you can see support for User, Object and other types:
For Azure, we support several custom mapping schemes e.g.
CostCenterEmployeeOrg=Department|Name=${CostCenterEmployeeOrg}- this maps employee Cost Center in Azure to Department attribute in your schema, where department is a reference and the lookup happens by name
EmployeeManager=ManagerObject|Name=${EmployeeManager}
OnLink has below configuration parameters:
config:data_limit=100 set to 100 for testing purposes, max is 1500. Each scheduled job processes a max of 1500 records. OnLink automatically fetches the next set of data in the next scheduled run.
config:export_azure_groups=true
config:export_azure_licenses=trueOnLink 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 “Get Data Completed” message in Job Logs. Then click on Import. For production runs, you can schedule the job and OnLink runs the GetData step as per your configured schedule. OnLink automatically runs the Import step every hour.
