About Action Paths

This article provides an overview of Action Paths, explaining their initiation methods and capabilities.

Understanding Action Paths:

Action Paths serve as containers for Flow Actions, representing sequential steps in response to a Trigger, Job, or Action Code. They play a pivotal role in defining the workflow for automated processes.

Initiating Flow Actions:

Action Paths offer versatile initiation methods:

1. On-demand using an Action Code:
   1. Users can manually trigger specific flow actions by entering an action code.
2. Through Job execution:
   1. Action Paths can be associated with jobs for activation, either:
      1. On-demand: as part of scheduled or ad hoc job executions.
      2. On a predefined schedule: to automate actions at specified intervals through job scheduling.
3. Automatically based on triggers:
   1. Action Paths can be associated with triggers that automatically set off flow actions. Triggers may operate on events, time, or data-driven conditions

Sequencing and Workflow Orchestration:

Action Paths ensure the sequential execution of flow actions, enabling precise workflow orchestration. Users can define the order and dependencies of actions for better control and synchronization.

Cascade Effects and Triggered Actions:

Flow actions within an Action Path can trigger additional actions or initiate other Action Paths. This allows for complex workflows with interconnected automation.

For more information read: 

Creating an Action Path