What the best practice to show local actions from the Actions Menu picklist, as a stage in the primary flow or as an Alternate stage?
You cannot explicitly model “optional local actions” in Pega Blueprint today.
Blueprint focuses on process intent, not UI-level action configuration. Optional local actions are inferred later during App Studio / UX design, not defined directly in Blueprint.
We try to represent the Optional actions in Alternate stage with Stage name prefix with “OPT: Transfer Assignment“ during the HI-FI Blueprint session
Hi @ScottD17733710 : Welcome to community.
Blueprint does not currently have native support for “optional actions” at the state level. As a workaround, you can add additional steps within your desired stage or process and label them clearly as “Optional Action” so that end users recognize these are not mandatory for progression. This will help to make sure you have captured all details of the process in the blueprint. During upload, system will help you to generate required rules for the optional actions too and the system architects can re-arrange them as required.
In this way, you will be creating a high fidelity blueprint and will leverage on the rules created by it.
Thanks.