How do local actions differ from optional processes?

Local actions are designed to enhance user interaction within a flow by allowing users to perform tasks without completely diverting from the main process. When a local action is executed, the user can perform certain tasks while still remaining within the context of the primary flow. After the completion of the local action, it returns the user back to the primary path of the process, ensuring a seamless workflow and maintaining the integrity of the primary process.

In contrast, optional processes are separate entities. They can be invoked as needed, but they represent a distinct flow rather than a continuation of the primary path. When optional processes are executed, they do not necessarily lead the user back to the primary flow once completed; they might lead to a different outcome or continue along a separate path altogether.

This distinction is crucial when designing a user experience, as local actions are integral to the main process whereas optional processes provide additional functionality that may or may not be relevant to the user at that point in their workflow.