3.5.0 Execution Flows – How can we help?

Abbreviations, used in manual:

EF - Execution Flow

In Quality Gates module, Under the 'My Projects' menu item, choose a specific project, then navigate to the 'Execution Flow' module.

EF refers to the sequence of steps that can be executed in a particular order or in parallel, to perform a specific action or process. It is a visual representation of the steps involved in completing a task, such as extracting data from a source, transforming it into the desired format, and loading it into a target destination. The EF could be a sequence (or circularity) of Tests, Scripts, and EFs that can be executed in any desired order.

The EF canvas includes several customized options in addition to the flow itself (EFs, Tests, Scripts), designed to help the end-user tailor the EF to their needs, including results, alerts, and other configurations:

Adding Entities to EF

The EF canvas provides great flexibility for designing workflows by allowing you to add the following types of entities:

Nested EFs – other EFs embedded within the current EF, enabling modular design and workflow reuse.
Tests – automated checks that validate specific conditions, requirements, or criteria within the workflow.
Scripts – code snippets or commands that perform specific tasks, offering advanced customization and automation options.
Notes – freeform text annotations used to document, explain, or provide context to parts of the EF, enhancing readability and collaboration.

Notes Example (Yellow Blocks):

Each entity can be dragged from the Toolbar onto the EF canvas. Once added, you can connect the entities to define execution order, dependencies, or logical relationships, tailoring the flow to your specific needs.

Connection Types Between EF Entities

Connections between entities in an EF define the logic and conditions for executing subsequent steps. The following connection types are available:

Success - Executes the next entity only if the previous one completes successfully.
Complete: Executes the next entity after the previous one finishes, regardless of success or failure.
Failure: Executes the next entity only if the previous one fails.
Warning: Executes the next entity if the previous one ends with a warning.
Execution Failure: Executes the next entity if there is a failure in the execution process (distinct from logical failures).
Always: Executes the next entity unconditionally, regardless of the outcome of the previous one.
OR: Executes the next entity if any of the connected conditions are met:
1. Select OR as the connection type from the dropdown menu.
2. A checklist of conditions will appear.
3. Check the boxes for the desired conditions (e.g., "Success" or "Failure").
4. Confirm your selection by clicking the checkmark.
By using the OR connection type, you can combine conditions for greater control and flexibility within your Execution Flow.

By selecting the appropriate connection type, you can tailor the EF to meet specific requirements, ensuring optimal control over execution logic.

Top Toolbar:

Flow Enabled switcher - allows to disable (EF won't run) or enable current EF. By default is on.

Scheduler button - EF can be scheduled to run automatically on chosen date and/or time:

Please refer to the Scheduler manual for more details: Execution Flows Scheduler

Enable Circularity – allows running the EF entities in a loop (be careful to avoid an endless loop). Should be set "Node To Start With" (EF's object that will be a start point for circularity) and "Stop After" (how many times a loop should be implemented). A numeric variable in format @var_name; can be used in the field "Stop after … iterations".

For Example:

Using circularity to run an EF for 2 iterations, run/execution results will be shown for each iteration:

Disable AND - when an EF's item has more than one entrance connection and the switcher is Enabled (by default) => the item will run only if all the previous connections will finish (according to their conditions).

When the switcher is Disabled => every connection will run separately, the same as a regular EF.
It means that the object can be implemented more than once (there is no dependency between the connections).

Please refer to the Disable AND detailed manual: Execution Flows - AND Operator

Toolbox: