ADP Workforce Now to JSM Assets

Configure the connection to ADP Workforce Now by going to OnLink (Manage your apps) - Connections. Then click on Add System and select “HR/Other Assets Sources”.

To connect ADP integration, you must get ADP's information: Client ID, Client secret, Private key, and Certificate (public key). Here are the instructions from ADP to generate the certificate pair: https://developers.adp.com/learn/how-to-articles/generate-a-certificate-signing-request#manual-process-steps-(client-process-steps) - follow the “Manual Process Steps (Client Process Steps)” instructions in this link.

For Client ID and Client Secret contact your ADP client representative if you don't have this information.

Once you have completed the above, configure the connection in OnLink:

Once connection is established, 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 mapping configuration:

key:workerID.idValue=Worker ID
map:person.communication.emails.0.emailUri=Email
map:person.legalName.givenName=First Name
map:person.legalName.familyName1=Last Name
map:workerDates.originalHireDate=Hire Date

Here’s a breakdown of some of the mapping configuration items:

Key or Map	Description

Key or Map	Description
`key:workerID.idValue=Worker ID`	The keyword “key” refers to using Worker ID as a unique identifier. This allows OnLink to update the record.
`map:person.communication.emails.0.emailUri=User`	Maps email to User which can be an attribute of type User
`config:filter=/mobileUserAccounts/organizationOID eq 'ABCDEFGH'`	Set filter to limit workers returned

Any other field returned by the API can be used in the mapping. See this link for a full list of available API fields: Get Workers API

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.

Additional field mapping examples:
map:person.legalName.familyName1=Last Name
map:person.preferredName=Preferred Name
map:person.legalName.givenName=First Name
map:person.communication.emails.emailUri=Email
map:businessCommunication.emails.0.emailUri=Work Email
map:person.legalAddress.countryCode=Country Code
map:workerStatus.statusCode.codeValue=Worker Status
map:workAssignments.0.hireDate=HireDate
map:workAssignments.0.positionID=PositionID
map:workAssignments.0.reportsTo.0.positionID=Manager Position ID
map:workAssignments.0.reportsTo.0.reportsToWorkerName.formattedName=Manager Name
map:workAssignments.0.payrollGroupCode=CompanyCode
map:workAssignments.0.homeWorkLocation.nameCode.shortName=Office
map:workAssignments.0.homeWorkLocation.address.countryCode=Country
map:workAssignments.0.jobCode.longName=JobTitle