/
ADP Workforce Now to JSM Assets

ADP Workforce Now to JSM Assets

ADP Workforce Now Connection Setup

Overview

Use this guide to connect ADP Workforce Now to OnLink, configure an Assets import, map ADP fields to Assets attributes, and test the import process.

In OnLink, go to Manage your apps > Connections, select Add System, and choose HR/Other Assets Sources.

Prerequisites

Before creating the connection, collect the following ADP integration details:

  • Client ID

  • Client secret

  • Private key

  • Certificate/public key

To generate the certificate pair, follow ADP’s ADP Developer Resources.

If you do not have the Client ID or Client Secret, contact your ADP client representative. If you use the OnRamp Cloud version and receive the Client ID and Client Secret through Onward, set both the public and private certificate values to USE_ONWARD_PARTNER.

Create the Connection in OnLink

  1. Open OnLink from Manage your apps.

  2. Go to Connections.

  3. Click Add System.

  4. Select HR/Other Assets Sources.

  5. Enter the ADP credentials, private key, and certificate details.

  6. Save and verify that the connection is established.

Use the screenshot below as a reference when entering the ADP connection details.

image-20240827-004743.png

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

The table below explains the key mapping and configuration item types.

Item

Purpose

Item

Purpose

key:workerID.idValue=Worker ID

Uses Worker ID as the unique identifier so OnLink can update the correct Assets record.

map:person.communication.emails.0.emailUri=User

Maps the worker email to the User attribute. The target attribute can be an Assets User type.

config:filter=/mobileUserAccounts/organizationOID eq 'ABCDEFGH'

Limits the workers returned by ADP. Additional examples:

config:filter=workers/person/legalName/familyName1 eq 'Smith' config:filter=workers/workAssignments/assignmentStatus/statusCode/codeValue eq 'A'

config:api=/hr/v2/worker-demographics

Optional. Changes the default /hr/v2/workers API to worker demographics.

Test and Run

OnLink processes data in two steps: Get Data and Import Data.

  1. Click Get Data.

  2. Wait until Job Logs show: No more pending records. Data will be imported on next Import run.

  3. Click Import.

  4. For production, use the schedule you choose. Production runs are fully automated.

image-20240318-045922.png

Additional 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:jsonpath__workAssignments.*.hireDate__where__workAssignments.*.primaryIndicator_eq_true=HireDate map:jsonpath__workAssignments.*.reportsTo.0.positionID__where__workAssignments.*.primaryIndicator_eq_true=Manager Position ID map:jsonpath__workAssignments.*.reportsTo.0.reportsToWorkerName.formattedName__where__workAssignments.*.primaryIndicator_eq_true=Manager Name map:jsonpath__workAssignments.*.assignmentStatus.statusCode.shortName__where__workAssignments.*.primaryIndicator_eq_true=Assignment Status map:jsonpath__customFieldGroup.stringFields.*.stringValue__where__customFieldGroup.stringFields.*.nameCode.codeValue_eq_Windows Login=Windows ID

References