Creating a Digital Process
See how to design your custom process.
Using the Digital Processes dashboard, you can create, edit, and monitor your processes. The processes are made up of a combination of triggers and process steps. It is required to have at least a trigger in a digital process.
Process components
Triggers
Triggers are used to start new instances of a process, or resume an existing one that was paused. A number of commerce events are provided out-of-the-box, these are the CE events. Additionally, you can configure custom events for your tenant, which are then available in the list. CE events can only be used as starting triggers, while custom events can serve as both starting and intermediate triggers.
You can also use Timer Events as triggers. A timer event provides a flexible mechanism to schedule and control the execution of a digital process. It supports a wide range of trigger configurations to meet diverse timing and scheduling requirements. Similar to custom events, you can use timer events both as starting triggers to initialize a process, and as wake-up triggers to resume a process between steps.
Process steps
Process steps are Make scenarios or other digital processes that can be combined to create a single end-to-end automated process. The scenarios are configured for your tenant, and a list of available ones is displayed in the drop-down menu. Whenever a new scenario is created for the tenant, the list is automatically updated.
Building a process
Choose to create a digital process
Go to the Digital Processes dashboard and choose Create Digital Process. The process creation is initiated, allowing you to either select Start from a Template or Start from Scratch for the design.
If you choose Start from a Template, you can select the process template from the ones available in the Process Library. You can adjust the process to your needs based on the defined template triggers and steps.
If you choose Start from Scratch, you start your configuration with no configured triggers or steps.
The next steps follow the Start from Scratch process creation.
Choose a process trigger
Every process begins with a trigger event that starts the entire flow. A pre-configured list of events is available out-of-the-box to choose from. For example, the registration of a new customer can serve as such a trigger. The starting trigger can be both a CE event related to any commerce operation, or a custom event created in your tenant.
Add a process step
Once the trigger is defined, you can configure the subsequent steps in the workflow by selecting them from a list of available process actions. Use them to build the flow according to your business requirements. To start creating a new step, the add icon and then step.
The first thing you can choose as a process step is a Scenario that represents an action to happen. For example, when a new customer is created you want to welcome them with an email with some first account information. In that case, you use a scenario build for your tenant. You can either choose a fixed one, or configurable where you can do additional adjustments. For example:
Fixed scenario - you can just choose a scenario which completes the action that you want to happen. No additional adjustments are needed here. For example, sending a Welcome Email.
Configurable scenario - you still choose a scenario that completes the action but you can also add some additional configuration. For example, sending a Welcome Email but with a template adjusted to B2B or B2C customers.
Another possibility as a process step is Subflow. When you use subflows, it basically means that you are embedding a different digital process into the current one. What you see in the drop-down list are the digital processes already built in your tenant. An example of a subflow can be sending a coupon together with the welcome email for your new customers.
Whenever you want to remove a trigger or a process step, you can do so directly in the relevant block by choosing the Remove action under the three dots icon.
Using triggers between process steps
If your digital process needs to pause until a specific event occurs, it can enter a dormant or sleeping state. During this time, the process remains active in the background but does not continue to the next steps until a specific event happens.
To wake up a sleeping process instance, you need to add a trigger that allows the process to continue when the expected event occurs. When setting up such a trigger, you can place it between process steps. However, only custom events can serve as intermediate triggers. This means that if you select an event from the drop-down list to configure the trigger, the CE events are not be visible.
Last updated
Was this helpful?