Breadcrumb Steps Not Displaying All Assignments correctly

Hi Experts,

I have a case-wide supporting process called “Meter Flow”, which is launched through a Local Action. The flow consists of 4-5 assignments/screens, and some of these assignments are conditionally executed based on business logic.

The issue I am facing is related to the breadcrumb/step navigation displayed in Constellation. Currently, only a subset of the assignments (highlighted steps) are appearing in the breadcrumb, while the remaining assignments are not being displayed even when they are part of the supporting process.

I would also like to understand:

  • Are there any specific configurations or limitations in Constellation that impact breadcrumb visibility for conditional assignments?

  • Has anyone encountered a similar issue, and what approach did you use to ensure all relevant steps are represented correctly in the breadcrumb?

Any guidance or best practices would be greatly appreciated.

Thank you in advance for your insights.

So, what’s happening when we navigate to the step which is not present in the breadcrumbs? Is it then appearing?

No, the Last screen label value is only getting displayed.

What happens if you configure the flow as part of the case workflow? do you see the same issue? just trying to isolate the issue?

Breadcrumbs help users understand where they are. I’m wondering if conditionalizing steps might be overloading the purpose of the breadcrumb experience. Could the steps be simplified or generalized with the decisions happening within the step vs. within the process flow?

Also - it seems this process is looping over a list, checking for a completed state at the beginning and the end, which might point to a “split for each” approach. This post might be helpful with thinking through alternative approaches. The “hierarchical form” technique might be worth considering, too.

Personally I’ve never been a fan of Multi-step Forms (screenflows) and decision shapes for conditional steps. One minute I have 3 steps to do, then I have 5, then I have 4 - it gets very confusing very fast.

This isn’t a Constellation / UI Kit discussion, the design system across these architectures has always allowed decision shapes in the process.

Personally, if its a complex process like this, I would use a “normal” process, instead of multi-step (screenflow). In 8.8 we introduced Configuring navigation to a previous step, which allows any process to act just like a screenflow.

The added benefit, for a complex process, we don’t show breadcrumbs and confuse matters with an ever changing breadcrumb trail.