Synchronize users from ADP Decidium

  • Updated

Who can use this feature?

  • This feature requires the ADP Decidium Integration. Contact your Account Manager for more information.
  • Platform Administrators can activate the integration once it’s been enabled by their Solution Architects.
  • Accessible only on the Web Application.

ADP Decidium connector overview

This connector synchronizes your users from ADP Decidium to 360Learning. Upon activation, the integration will:

  • Add synchronized ADP Decidium users to 360Learning if they didn’t previously exist.
  • Edit existing 360Learning fields with the information from ADP Decidium.

💡 The integration will not delete or synchronize users who only exist in 360Learning.

Synchronization schedule

The synchronization starts automatically once a day at 01:00 AM Central European Time (CET/CEST).

Set up the integration

There are a few items you need to complete before you can start setting up the integration in 360Learning.

Step 1: Prerequisites

Contact your ADP Decidium representative and ask for the following items:

  • Access to the following ADP Decidium APIs for your tenant:
    • https://accounts.eu.adp.com/auth/oauth/v2/token
    • https://api.eu.adp.com/hr/v2/workers
  • API Decidium credentials
    • client_id
    • client_secret

For testing, you need to use sandbox-specific credentials from ADP, since production credentials won’t work in the sandbox environment due to a different security certificate.

Step 2: Contact 360Learning

After you have gathered the information listed above, email your 360Learning Client Success Partner or Solution Architect with the following information:

  • Integration Name: ADP Decidium
  • ADP Domain: Your ADP Decidium application URL
  • ADP API Keys: client_id, client_secret
  • 360Learning Group ID: Include only the IDs for the groups that you will sync with ADP Decidium.
  • 360Learning Connector Admin Email: The email of the user who will act as the administrator for your integration. In 360Learning, this user needs to be either a platform administrator or the platform owner.

After that, your Solution Architect will reach out and complete configuration and setup testing with you. Once testing is complete, they will turn the integration on in your live platform.

Step 3: Test the integration

Next, your Solution Architect will send you a URL to test the integration.

The test environment does not automatically synchronize from ADP Decidium and 360Learning. When running through your tests, contact your Solution Architect to manually run the synchronization scripts.

Example:

  • Production URL: myacademy.360learning.com
  • Test URL: myacademy.360mocc.com:14532

Other things to know about the test environment:

  • Any changes made in production will not show up in the test environment.
  • Any changes made in the test environment will not show up in production.
  • The test environment does not send any emails.
  • The test environment is temporary. If you cannot log in to it anymore while still testing your integration, ask your Solution Architect to restart the test environment.

Suggested test scenarios

💡 When running through your tests, remember to contact your Solution Architect to manually run the synchronization scripts.

  • All Active ADP Decidium users show up as Learners in your synced group(s).
  • The data from ADP Decidium was copied over to the correct 360Learning fields for each user.
  • When you modify a user in ADP Decidium, the edit shows up correctly in 360Learning after the sync.
  • When you create a new user in ADP Decidium, they show up in 360Learning after the sync.
  • When you terminate a user in ADP Decidium, they are deleted in 360Learning after the sync.

Step 4: Activate the integration in production

Once you’ve completed your tests, request for your Solution Architect to deploy the integration into your production platform.

Once the integration is in production, your platform administrators can activate it in the relevant groups:

  • If you don’t see hover behavior in the left sidebar, replace the first step with:
    1. In the left sidebar, click on the relevant group.
    2. At the top right of the main section, click gear.svg Settings.
  1. In the left sidebar, hover over the group you’re synchronizing data with, then click settings.svg Settings.
  2. In the left panel, select IntegrationsManage Integrations.
  3. Click ADP Decidium.
  4. Verify the API information is correct and click Setup integration.

New users added through the synchronization will get an email notification with an email and password they can use for their initial login. Once they’ve connected, the platform will prompt them to change their password.

Synchronization rules and data mapping

User status processing

We only synchronize users marked ACTIVE or INACTIVE in ADP Decidium:

  • Users set as ACTIVE in ADP Decidium will be created or updated in 360Learning.
  • Users set as INACTIVE in ADP Decidium will be deleted in 360Learning.

PENDING users are ignored.

Important note on user reconciliation

By default, users are reconciled (matched and synchronized) primarily via email address. This means the connector uses the user's email to identify and update their profile in 360Learning.

However, you have the option to configure the connector to prioritize the external ID (a unique identifier from your HRIS) for user reconciliation instead. This is recommended if your external IDs are the most reliable and consistent identifiers for your users.

Default provisioning and mapping

By default, new users are created with the learner role in the synchronization group. The table below shows the data mapped between the 2 systems.

ADP Decidium Worker field location 360Learning Learner Mandatory
associateOID externalId Yes
person.legalName.givenName firstName Yes
person.legalName.familyName1 lastName Yes
person.legalName.formattedName name Yes
businessCommunication.emails[0].emailUri mail Yes
workerStatus.statusCode.codeValue Determines status/action Yes
workAssignments.jobTitle job No
reportsTo[].associateOID managers[] No

Manager synchronization option: Manager/managee relationships are synchronized by default. To disable this feature, contact your SA or CSP.

Ignored user criteria

If a user you expect to be synchronized is missing, check the following criteria.

  • A user is rejected if their ADP payload is missing mandatory data or contains an invalid email format.
  • A user is ignored when they already exist outside the integration scope (located outside the synchronization group or one of its descendants), or if a user with the same email already exists in a different company instance on the 360Learning platform.

Optional features

Custom fields

In addition to the default synced fields, the integration can synchronize any ADP Decidium field from the payload returned by the ADP Decidium Workers API, including the following:

  • Sexe: workers/person/genderCode/shortName
  • Birth date: workers/person/birthDate
  • Hire date: workers/workerDates/originalHireDate
  • Start date: workers/workAssignments[itemId]/actualStartDate
  • Collaboration type: workAssignments[itemId].customFieldGroup.codeFields[itemID='collaborationType'].codeValue
  • Work arrangement: workers/workAssignments[itemId]/workArrangementCode

Keep in mind the following:

  • Custom fields do not need to exist in the 360Learning platform before synchronization; they are created on demand.
  • Custom fields containing date values (such as hire date or start date) are created as date type fields in 360Learning. All other custom fields are created as string type fields. Date values from ADP Decidium are expected in yyyy-MM-dd format.
  • If you remove a custom field from a user in 360Learning but not in ADP Decidium, the integration will add the custom field back to the user in 360Learning in the next sync.
  • If you delete a synced custom field from 360Learning but not ADP Decidium, the integration will recreate and add the custom field back to users in the next sync.
  • If you change the title of a synced custom field in 360Learning, the integration will create and add a new custom field for that field in the next sync. The renamed custom field will still exist in 360Learning, but it will be removed from synced users.
  • If you add a non-synced custom field to a synced user in 360Learning, the custom field will stay in place during syncs.

Filtering users

You can define filters to limit which users are processed based on values returned in the payload. 

Filters are applied only to active users by default. If you need to apply these synchronization filters to inactive users as well, contact your CSP to activate this setting.

Check out our blog for more L&D resources.

Was this article helpful?

0 out of 1 found this helpful


Have more questions? Submit a request