You may have heard that Learnsmarter is built on Flow. That’s not strictly true. Under the hood there are hundreds of thousands of lines of code, but most user interactions where you use some kind of wizard to complete a task do use flow. Learnsmarter makes those flows available to customers to modify if necessary to suit their needs.
There are two ways of doing this. The one you choose depends on the situation. Overrides are useful where maybe you have a number of custom fields you want to include in a standard data entry screen – maybe when scheduling a new course for example. In that case an override is usually the best way to go. Ideally you will add those fields to the flow you’re overriding using Dynamic Forms for Flow (you just drag the fields onto the screen). Learnsmarter flows are typically built as a series of flows and you don’t have to override every flow – just the one you want to change. And then everything ‘just works’, which is cool.
If you’re adding flows to an Experience Cloud page, then things aren’t necessarily quite so clear cut. Often you’ll be better off to start with an existing overridable flow, but use that flow as a template. This means that you can change the options Experience Cloud users see without impacting internal users.
Whatever you choose to do, our very strong recommendation is to document all your changes. What was the purpose of the change? Which flow elements did you change? What was changed within the elements that were updated? If you do this, then you’ll be hugely grateful if you, or someone else, comes back to this flow in two years’ time and needs to understand what was changed.
