Feature: Automated Learning Step Completion in Journeys

Product: Journey Paths

Setup Effort: Automatically Available

Targeted Production Date: March 14, 2026

Summary: Learning steps included in Journeys now auto-complete when users finish their training. This mends one of those pesky little irritations: users would complete a course, lesson, or program, but the Journey step would still appear incomplete because they never clicked "Complete Step" after they finished the training (anyone getting “To Do” vibes?) 👎

This auto-complete update means fewer false positives (i.e. “in progress” Journeys), cleaner completion metrics, and less work for both end users and admin 🙌

Note 1: This update only applies to Journeys distributed after this feature goes live. Journeys distributed prior will still require manual completion via the Journey recipient or admins running a MOM process to complete Journey steps en masse.

Note 2: In your configuration, confirm that learning courses, lessons, or programs are correctly associated with Learning-type journey steps. Auto-completion only works when this linkage is correct!

🔗 Release Note

Feature: Case List Customization

Product: Case Management (Workday Help)

Setup Effort: Automatically Available

Targeted Production Date: March 14, 2026

Summary: If your team lives in Workday Help, this is the “Finally!” release note. Case solvers can now configure their own case list workspace 🤓 They can choose which columns to display, reorder them, and filter by the fields Flags, Service Team, and Labels. This means high-volume teams can prioritize and triage cases at a glance instead of opening each one individually like it’s 2012 🦖

Since Flags and Labels are customizable fields, surfacing them as columns transforms them from reporting-only fields into actual workspace tools 👏👏👏

Setup:

🔗 Release Note

Feature: Correct Change Job

Product: Core HCM

Setup Effort: Automatically Available

Targeted Production Date: March 14, 2026

Summary: This feature delivers two big changes that usher in more flexibility for your Change Job experience.

First, if you've opted into the Change Job Templates enhanced UI, you can now correct three critical fields on completed events: Supervisory Organization, Headcount Change, and Position. These fields drive your position management during staffing changes, so being able to fix them when someone strays from your org's standard approach—without having to rescind and re-initiate the entire transaction—is a huge time-saver 🙌

Second, Workday delivers a brand new web service (EIB) called Correct Change Job, which lets you correct change job events en masse. This is especially handy if you accidentally pushed out changes in bulk that need tweaking ✍️

Why this matters even more: Remember that opt-in "out-of-order Change Job" feature that snuck in at the tail end of 2025R2? That feature added flexibility by letting you process Change Jobs events out of chronological order—but it also opened the door to more chaos since you can now insert retro changes wherever you want 🫠 This new Correct Change Job EIB gives you a way to adjust the events impacted downstream at scale. (Pro tip: maybe don't advertise this capability too loudly to your leaders 😅)

Notes: There seems to be some kinks getting worked out. Keep an eye on the release note!

🔗 Release Note

Feature: Coverage Waive Date for Enrollment Event Rules

Product: Benefits

Setup Effort: Setup Required

Targeted Production Date: March 14, 2026

Summary: Benefit teams, rejoice! Until now, waive dates within your Enrollment Event Rules were forced to follow the same logic as Coverage Begin Dates. Now they’re independent, giving you more control over when waived coverage actually ends.

This separation means you can better align coverage timing with your carrier rules and internal policy. For you U.S. Federal teams, this flexibility helps support strict FEGLI requirements without manual workarounds.

Setup:

Notes: If you don’t do anything, this new selection defaults to the value “On Coverage Begin Date” (which is what it was doing before).

🔗 Release Note

Feature: Distribute a Journey Using Any Business Process

Product: Journey Paths

Setup Effort: Setup Required

Targeted Production Date: March 14, 2026

Summary: Journeys are no longer boxed into a small set of supported BPs. With 2026R1, you can add the Journey Distribution Service as a step in any BP definition. That means you can finally trigger Journeys in whichever workflow your organization needs them: contact changes, absence flows, off-boarding moments, manager actions, and more 🤓

Setup: Workday delivers the framework automatically, but you need to have created the Journey first, then add the step to the relevant Business Process.

Note 1: As it stands now, existing BPs with Journeys need the Configure Journey Distribution Service redone for the new input or the BP will error out ⚠️ Plan to test early and expect some cleanup as Workday finalizes the fix.

Note 2: Terminated workers can’t access Journeys. So, keep this in mind if you add a Journey to the Terminate Employee BP now that its an available option!

🔗 Release Note

Feature: Report As A Step Type

Product: Journey Paths

Setup Effort: Automatically Available

Targeted Production Date: March 14, 2026

Summary: You can now add Reports directly as Journey steps. That allows the "Here's what you need to review" moment to happen exactly when it should—in the workflow! That means fewer scavenger hunts for users and admins, and a more consistent execution when a process depends on a specific view of data.

Combined with the ability to add a Journey to any BP, this is one of those “sky’s the limit” upgrades! ☁️

Here is what the report step looks like in action for a new manager getting up-to-speed on their team’s feedback.

Note: The person going through the Journey still needs the right domain security to actually run the report and view its content.

🔗 Release Note

Feature: Restrict Job Profile Visibility by Country and Organization

Product: Core Human Capital Management

Setup Effort: Automatically Available

Targeted Production Date: March 14, 2026

Summary: Job Profile restrictions just got more powerful! In addition to Country (which was delivered in a previous release), you can now restrict Job Profile visibility by the organizations Sup Org and Company.

This means you can configure your Job Profiles such that when you’re assigning them during staffing transactions—like Hire, Change Job, or Edit Position—only the relevant ones appear in the pick list 🎯 This feature is especially helpful for multi-company tenants that need tighter guardrails around which Job Profiles can be used where/when.

Here's how it works: Workday checks the worker and/or position's assignments and only shows Job Profiles that match. Country restrictions must match the country of the assigned Location, while Sup Org and Company restrictions must match the org assignments. If the Job Profile restriction fields are blank, that Job Profile stays available for selection everywhere.

Setup:

In the tasks Create Job Profile or Edit Job Profile, add a Country and/or Organization restriction under the section Category Details.

Note: Subordinate sup orgs can’t be excluded when restricting by supervisory organization—the job profile is available for selection within the whole chain.

🔗 Release Note

Feature: Update Marital Status in Benefits Enrollment Questionnaire

Product: Benefits

Setup Effort: Setup Required

Targeted Production Date: March 14, 2026

Summary: Here comes consolidation! You can now update marital status directly within the Benefits Enrollment Questionnaire (alongside Tobacco use), and the selection automatically completes a related Personal Information event in the background 🎉

Previously, marital status lived solely in Personal Information, which then required employees to take an additional step after finishing their benefit enrollment for that related life event. Spoiler alert: they often didn’t, so Benefits and Core HCM data quickly fell out of sync.

This new workflow is much more intuitive. Since marital status changes are almost always triggered by benefit (or tax) implications, capturing the update right where employees already make those elections and consolidating the two processes means more accurate, timely data—and cleaner data hygiene overall ✨

Setup:

Note: The update isn’t bidirectional. Changing marital status in the Personal Information change task first doesn’t auto-complete or trigger anything on the benefits side (unless you configured a unique workflow for your org).

🔗 Release Note