Transition types describe the manner or method by which a system moves from a trigger to an action.
Default
This is the standard or primary transition that is taken when no specific conditions are met. It's the "fallback" transition, ensuring that there's always a path from the trigger to an action even if no other criteria are satisfied.
Condition
This transition type is based on a specific condition or set of conditions being met. Only when the condition(s) evaluate to true does the transition lead to the associated action. For instance, a condition might check if a user is logged in before allowing access to a particular resource.
JS Expression:
InputData.PAYLOAD_FIELD_NAME.ToString() === 'VALUE' The highlighted fields below will change depending on the condition and the payload
Delay
This transition introduces a waiting period between the trigger and the action. The action will only be executed after a specified amount of time has passed since the trigger was activated. For example, a delay transition might be used to wait for 5 seconds after a button is clicked before displaying a pop-up.
Bookmark
This transition type allows for a process to be paused and resumed at a later time. When the trigger is activated, the system marks or "bookmarks" the current state. The action can then be executed later when the process is resumed from the bookmarked state. This is useful in scenarios where manual intervention or approval is required before proceeding.
Real life examples
Transition Type | Scenario | Visual Depiction |
Default (no condition/delay) | Every month, when pAIment processes John's subscription fee, engAIge awaits a payment status update. As soon as engAIge receives the trigger from pAIment it will kick off action to send John an SMS to remind him to pay. |
|
Condition | Upon receiving the payment status update from pAIment, engAIge uses a condition-based transition to check the payment status for the 3rd month. If pAIment sends a "Payment Failed" status specifically for the 3rd month, the condition is met, and engAIge triggers the action to send John an SMS notifying him of the missed payment. If the payment is successful or if it's not the 3rd month, no SMS is sent. |
|
Bookmark | Let's say pAIment's status for John's 3rd-month payment is "Pending" due to bank processing delays. Instead of immediately deciding on the action, engAIge uses a bookmark transition to pause the workflow. Once the payment status is updated by pAIment (either successful or failed), engAIge resumes from the bookmarked state and checks the condition again to decide on sending the SMS or not. |
|
Delay | After receiving a "Payment Failed" status for John's 3rd-month subscription, engAIge introduces a delay transition of 48 hours. This gives John a grace period, perhaps allowing him to resolve any bank issues or fund shortages. If, after the delay, the payment is still not received, engAIge triggers the action to send John the SMS about the missed payment.
|
|
Example of an workflow created in the Automator
