Learning Paths Update: More Flexibility, Less Workaround

Learning Paths just got a significant upgrade. If you've ever had to nest paths inside paths to get the structure you wanted, or held off making a change because learners were already registered, this update is for you. Here's what's new.

One path, any structure

Previously, Learning Paths came in two flavors: serial (complete everything, in order) or grouped (choose from a set). If your program needed a bit of both like three required courses and a "pick one of four" elective, then you had to nest separate paths together to make it work.

That requirement is gone. Instead of nesting a Learning Path within a Learning Path to provide this mix, you can instead create it all in one Learning Path via the new ‘Option Group.’ Meaning, for any Learning Path you can:

1. Create a single required objective or series of them to ensure each learner completes the objectives in order.
2. Create an Option Group and
   1. Set the required objectives to be completed to be less than the objectives added to the group - this enables learners to choose which objective they will complete to progress.
   2. Set the required objectives to be completed to be the same as the amount of objectives in the group - this enables admins to say that all objectives are required, but the learner could complete them in any order.
   3. Set the required objectives to be completed to be ‘0’ - this makes it so that the objectives within are completely optional for the learner.

The result: you can build a path that says "complete these three objectives, then choose one from this group of four," all in one place, no nesting required.

Edit active paths, even with learners already on them

Previously, once learners registered, a path's objectives were locked. Now you can add, update, or remove objectives at any time, on any path.

A few things to know about how changes land for learners already in progress:

1. Adding an objective simply adds it to everyone's progress page.
2. Updating one (like swapping the course) clears existing progress for that objective, with a warning before you confirm.
3. Removing one deletes it and any related progress, and overall completion recalculates automatically.

Draft paths remain freely editable with zero impact, as before. The difference is that active paths are no longer frozen — just be mindful that structural changes now propagate to everyone on the path, including learners who'd already finished that objective.

Pin specific events to a course objective

Course objectives used to leave learners free to book any upcoming event for that course. Now you can restrict a course objective to a specific date or set of dates, so learners only see the events you've approved for them to select. That restriction is honored everywhere a learner books: the admin registration modal, the Bookings/Opportunity flow, the WebLink catalogue, and LMS bookings.

Smaller changes that add up

A handful of quality-of-life improvements round out the release:

1. Drag-and-drop ordering — reorder objectives, or drag them into and out of option groups, without rebuilding the path.

1. Richer objective details — objectives with multiple achievements, categories, or events now show the first item plus a "+N more" you can hover to expand.
2. Refreshed registration and progress views — the learner registration modal auto-selects an event when there's only one option, and the learner progress page now mirrors your path's grouping, with clear warnings on anything still outstanding.

1. Active-only by default — the Learning Path list now hides inactive paths out of the box (you can still switch the filter), which should cut down on clutter for anyone managing a large catalogue.
2. True duplication — copying a path now copies its objectives and steps in full, as you'd expect.

For developers

Existing integrations using updateLearningPaths will keep working unchanged. To take advantage of mixed required/option grouped structures, you'll want the new setSteps mutation, which defines steps and their minimum-required counts and order directly — this is what powers the new flexible objective model, including what serial paths used to handle.

The bottom line

The old serial-vs-grouped divide, and the "no edits once learners are in" rule, were the two biggest sources of workarounds in Learning Paths. Both are gone. You get one flexible structure for any program design, the freedom to keep improving a path after launch, and tighter control over which events learners can book — all with a cleaner interface to manage it in.