Issue

By introducing the ability to handover a workflow, we've eliminated the need to repeat identical steps in multiple flows, thereby saving time, effort, and reducing the potential for errors. This approach is efficient and effective, especially when dealing with complex processes that involve complex flows.

Product

• Mobile Marketing Cloud
• Customer Data Platform

Resolution

No trigger workflow type

This workflow type serves as a common endpoint for multiple processes. It's where different workflows come together. You can connect other workflows to this one using the 'Enroll to Workflow' step.

Important Points:

• You can't use the 'Enroll to' step in a 'No Automatic Trigger' workflow. This prevents endless loops in your processes.
• If you change a workflow to 'No Automatic Trigger,' it will remove any enrollment steps. You'll get a confirmation prompt before this happens.
• If a 'No Automatic Trigger' workflow has dependencies, you cannot change the trigger type. The dependencies are shown in the trigger and from here you can navigate to the workflows that hold the link.
  

In the 'No Automatic Trigger' step, you can decide whether a profile passes through the flow once or multiple times. By default, the setting allows the profile to pass only once for security and efficiency reasons.

Enroll to workflow step

With this step, you can smoothly transfer a workflow to the central endpoint. In the dropdown menu, you'll find a list of all workflows configured with a 'No Automatic Trigger' setting. Selecting from this list streamlines the handover process, ensuring a seamless transition to the common endpoint workflow.

Why is the useful?

• By centralizing common ending steps, you eliminate the need to duplicate these steps in every individual workflow. This significantly reduces redundancy in your workflow configurations.
• Managing changes and updates becomes much simpler. Instead of modifying the same steps in multiple workflows, you only need to update the centralized workflow. This ensures consistency and reduces the risk of errors.
• All processes ending in the same way remain consistent across various workflows. This consistency is essential for quality control and standardization of outputs.
• Workflow designers can focus on the unique aspects of each workflow without worrying about repetitive ending steps. This streamlines the design process and allows for better organization of tasks.
• As your organization grows and more workflows are added, having a centralized ending point ensures that scalability is easier to manage. New workflows can simply be directed to enroll in the existing centralized flow.
• Centralizing common steps allows for better error tracking and management. If an issue arises in the common ending steps, it can be identified and resolved more efficiently.
• Collaboration between teams and departments is enhanced, as everyone is aligned on the common ending steps. Teams can work more cohesively knowing that their individual workflows seamlessly integrate at the end.