Skip to main content

LMS Integration - Workday

Learn how Arist writes completions back to Workday Learning, so each learner Arist course lands on their worker record and their learning history stays complete in one place.

Platform access level: Org Admins


Writing completions back to Workday Learning puts each learner's Arist course onto their worker record, so their learning history stays complete in one place. The writeback runs outbound, after learners finish training in Arist, over the same connection used for the inbound worker sync. This guide is written for the IT and Workday administrators who set it up.

Note: This writeback is on the roadmap and targeted for end of year. The inbound worker sync is the live production path today, so treat this guide as the target-state design and confirm the current status with your Arist contact before you rely on it.


1. Completion writeback overview

Learning created in Arist is written back into Workday in two stages, first the course record and then each learner's completion against it, so the activity is captured on the worker's learning record. The course is published to your Workday Learning catalog first, and completions post against it afterward.


2. Publishing the course to Workday Learning

When a course is first built in Arist, it is sent to Workday Learning as learning content for an administrator to make available in the catalog. This is what gives completions something to tie back to.

Important: A completion cannot be recorded against a course that has not been created. Publish and make the course available before its learners begin, so their completions have a catalog record to attach to.

The exact operation and content type are set in your connector at onboarding.


3. Recording completions on the worker record

As learners complete courses in Arist, Arist collects the newly completed enrollments, in pages of up to 500, and the integration layer sends them back to Workday Learning. For each completed enrollment, it builds a Workday payload that maps the enrollment to Learning_Enrollment_Data.ID and the learner's external identifier to Learner_Reference, retrying a transient failure twice before it stops.

The batch is posted to Workday Learning as an asynchronous bulk import through Import_Learning_Enrollment, which returns an Import_Process_Reference_WID. Workday validates and records the enrollments on each worker's learning record. The integration then polls the import status with Get_Import_Processes and Get_Import_Process_Messages, a step planned as part of this flow.


4. Endpoints Arist writes to

The writeback uses one course-publishing call and one completion call, both on the Workday Learning web service. Share this list with your security team, and apply any IP allow-listing your policy requires.

Stage

Endpoint

Publish course content

Put_Learning_Content (Learning, v44.1 WWS)

Import completions

Import_Learning_Enrollment (Learning, asynchronous bulk; returns Import_Process_Reference_WID)

Poll import status (planned)

Get_Import_Processes, then Get_Import_Process_Messages


5. Write access the ISU needs

The Integration System User Arist runs as must hold the domain permissions to create learning content and record completions. In practice this is the Manage: Learning Content permission for publishing the course and the Process: Learning Enrollment permission for recording completions.

Important: Without write access scoped to the Workday Learning web service, course and completion records cannot post back to Workday. Scope the ISU only to the web services and domains this integration needs, so it holds the least access required.


Related articles

  • HRIS Integration - Workday

  • Arist and Workday - Technical Guide

Note: Need help at any point? Reach out to your Arist Customer Success contact, or email [email protected].

Did this answer your question?