Overview
Scenario step is a defined action which happens as a part of a business process. Steps are described with:
- Name - a description name of the step. For example, “Get open orders”, “Send an email”, or “Start another scenario”
- Step type - determines a type of action that should happen.
- Input mapping - determines which data should be used as an input for the given step
At this moment, the following step types are supported by the platform:
- Agent - autonomous tool capable of performing various tasks, like sending emails, moving data, or interacting with CRM/ERP/OMS.
- Condition - allows executing different parts of the scenario depending on some condition, e.g. order being in a certain status.
- Wait - wait specified amount of time (seconds, minutes, hours, days) before proceeding to the next step.
- Event - wait for an external event to happen (e.g. manual approval, API call) before proceeding to the next step.
- Repeat..until - repeat the given set of steps until the provided condition is not met. For example, wait for a particular order status is reached or process order lines until no new lines are available.
- Group - group the incoming array of data by a certain feature. For example, group opened and closed orders.
- Combine - take input from different steps and combine into a single array or object.
- Split - take input in a form of array and apply given steps to each item separately.
- Start scenario - launch another scenario from this one.