​
Summary

The Workday integration allows you to push content to Workday and track user progress. Content pushed to Workday is seamlessly integrated with other content available to the Workday tenant and discoverable by multiple filtering options. Workday auto-completes content when a user launches it from the Workday UI. Content and Completions within Workday

​
Key Details

​
Content Upsert

  • Deduplication: Workday uses both external_reference and content title for deduplication. Ensure both are unique during content creation.
    • If a title matches existing content, the external_reference will be updated.
  • Implementation Notes:
    • Cover Images: Workday requires base64 encoded images. The integration handles URL conversion, failing the upsert if the download fails.
    • Accepted Enum Values:
      • Languages: Locale codes (e.g., en_gb).
      • Result: pass or fail.
    • Course Context: All content is within a course.
      • A course wrapper is automatically created.
      • Default course settings: Lesson Order 1, Lesson Mandatory True, Registrable Status Open.
      • Content is set to require enrollment by default.
      • Content categorization is customer-specific; see the categories endpoint.
    • Categories: Content must be pushed with a Workday category. This can either be a custom category added by the customer or a category from the list/get categories unified endpoint.

​
Completion Push

  • Uses learning_object_external_reference for content identification.
  • Content is set to require enrollment by default. This can be configured at an account level. If Enrollment Required (Content) is set to No, users can launch content without enrollment, which will cause automatic completion creation.

​

Provider-Specific Quirks
  • Content Categorization: Content may be categorized as internal, even if it links to an external provider.
  • Enrollments and Completions: Workday auto-creates these, potentially causing discrepancies.
    • Mitigation:
      • Completions update existing records rather than creating new ones.
      • A DELETE user completion endpoint is available.
      • A SCORM course blocker can be used.

​
Integration Configurations

​
Scorm Course Blocker

Workday fires automatic completions when a user launches a course from the UI. If the Workday course is a single content item (i.e. one lesson within the course) Workday will also complete the course at this point. This means that there will often be a discrepancy between the real user progress on the course in the external content provider and the completion status in Workday. Workday doesn’t allow configuration on this but we can provide a Workday approved worka-around. This will require your customer to upload a Scorm file to the Workday system which will contain a PDF instructing the user to return to and complete any previous lessons on the external content provider page before completion the Scorm lesson. As a result it blocks the completion of the course where it would normally auto-complete. The flow is outlined below:
images/diagram-export-20-03-2025-10_40_01.png

​
Mobile Content Lesson

Workday doesn’t support the use of additional mobile friendly content urls with a lesson. In order to help support this we can create an additional duplicate lesson in the content with a mobile specific url. There are 2 steps to enabling this:
  1. Configure the **Create Duplicate Content for Mobile **to Yes in the Integration Configuration
  2. Include a value in the Mobile Launch Content URL field.
images/Screenshot2025-03-20at10.57.44.png

​
Limitations

  • Rate Limits: 5-10 requests per second.

​
Testing and Validation

  • Standard testing procedures apply.