Types of Run

Path Run

1. Open a Flowchart
2. Click on any node and click on Automate
3. Click Run at the top right.
4. This brings up the Run dialog.
5. Set the Browser, Start URL etc.
6. You can check any combination of:
   • Run Normal Path
   • Run Positive Validations
   • Run Negative Validations

Depending on what you chose, multiple browsers may open up and execute the flows.

Flowchart Run

1. Open a Flowchart
2. Click on Run button at the top.
3. The rest is similar to Path Run.

Path Execution Order

The execution order of paths in a flowchart is automatically decided by Flowcharts.
This is mostly the natural order in which the paths were added to the flowchart.
However, if you wish to change the order, you can do it as follows:

1. Click on the dropdown arrow to the right of Run button and choose Execution Order
2. This shows the paths in a tabular format.
3. Each row has a draggable handle at the left. Drag and drop to re-order the paths.
4. When a flowchart is run, the paths will be triggered in the specified order.

Depends - Path Dependency

• Execution Order specifies the order in which paths are triggered for execution.
• In case of sequential execution, this will work fine.
• However, in case of parallel playback, it is not guaranteed that path 2 will start only after path 1 finishes.
  The only guarantee is that path 2 will be started after path 1 is started.

If more control is needed, we can use Path Dependency.

1. On the Execution Order dialog, Click on "Depends On" near a path (path 2).
2. Choose the other path that it depends on (path 1).
3. Click Save.
4. In this case, Path 2 will execute only if Path 1 has executed and has passed. Else Path 2 will be skipped.
   For example, we don't want to run other flows which depend on a successful product creation, if product creation itself is failing.
   This will save build time and give faster feedback.

Prerequisites at Path Level

When a flowchart is run with distributed playback, any path may be assigned to any available node. However, different nodes may have different add-ons and licenses available.
For example, a path that requires ANDROID mode might get assigned to a node that doesn't have the Mobile Add-on or its license, leading to unwanted failures.
This is where prerequisites come in. By specifying prerequisites at the path level, you ensure that each path runs only on nodes that meet its required capabilities.
1. In the Table View dialog, navigate to the Truth Table View or Execution Order, then click on Prerequisites located near the Login and Validate - Browser Android Flow.
2. This will open up the Prerequisites dialog.
3. Set the necessary prerequisites in the dialog. Click Update. The Execution Order dialog will reflect the change in prerequisites.
4. In this case, path Login and Validate - Browser Android Flow will execute only on a node which has the BROWSER mode and the ANDROID mode with 2 device instances.
   
5. We can also specify multiple browsers with their instances for a particular path. For example, in the case of path Browser Flow chrome and firefox, one instance of chrome and 2 instances of firefox are specified in prerequisites.
   Path Browser Flow chrome and firefox will run only on the node which has atleast one instance of chrome and 2 instances of firefox available for run.
   The path execution will start with the default browser type.
6. To run a path on a specific node, we can specify the node tag in prerequisites. For example, in the case of path Login and Validate - Windows Browser Flow, BROWSER mode and windows10 node tag are specified in prerequisites.
   Path Login and Validate - Windows Browser Flow will run only on the node which has the BROWSER mode and the windows10 tag.
infoNote: one can set the node tags in sahi.node.tags in sahi.properties

Project Run

1. Open a Project
2. Click on Run button at the top right.
3. The rest is similar to Path Run and Flowchart Run.

Flowchart Execution Order

The execution order of flowchart in a project is automatically decided by Flowcharts.
This is mostly the natural order in which the flowcharts were created in the project.
However, if you wish to change the order, you can do it as follows:


1. Click on the dropdown arrow to the right of Run button and choose Execution Order
2. This shows the flowcharts in a tabular format.
3. Each row has a draggable handle at the left. Drag and drop to re-order the paths.
When a project is run, the flowcharts will be triggered in the specified order.



Depends - Flowchart Dependency

• Execution Order specifies the order in which flowcharts are triggered for execution.
• In case of sequential execution, this will work fine.
• However, in case of parallel playback, it is not guaranteed that flowchart 2 will start only after flowchart 1 finishes.
  The only guarantee is that flowchart 2 will be started after flowchart 1 is started.
If more control is needed, we can use Flowchart Dependency.

1. On the Execution Order dialog, Click on "Depends On" near a flowchart (flowchart 2).
2. Choose the other flowchart that it depends on (flowchart 1).
3. Click Save.
4. In this case, Flowchart 2 will execute only if Flowchart 1 has executed and has passed. Else Flowchart 2 will be skipped.
   For example, we don't want to run other flowcharts which depend on a successful product creation, if product creation itself is failing.
   This will save build time and give faster feedback.
infoA dependency will not be honored if it appears below the chosen flowchart in the execution order. To ensure it takes effect, move the dependency above the chosen flowchart.

Prerequisites at Flowchart Level

When a project is run with distributed playback, any flowchart may be assigned to any available node. However, different nodes may have different add-ons and licenses available.
For example, a flowchart that requires ANDROID mode might get assigned to a node that doesn't have the Mobile Add-on or its license, leading to unwanted failures.
This is where prerequisites come in. By specifying prerequisites at the flowchart level, you ensure that each flowchart runs only on nodes that meet its required capabilities.
1. In the Execution Order dialog, Click on Prerequisites near a flowchart Checkout.
2. This will open up the Prerequisites dialog.
3. Set the necessary prerequisites in the dialog. Click Update. The Execution Order dialog will reflect the change in prerequisites.
4. In this case, flowchart Checkout will execute only on a node which has the BROWSER mode and the ANDROID mode with 2 device instances.
   
5. We can also specify multiple browsers with their instances for a particular flowchart. For example, in the case of flowchart Create Coupon, one instance of chrome and 2 instances of firefox are specified in prerequisites.
   Flowchart Create Coupon will run only on the node which has atleast one instance of chrome and 2 instances of firefox available for run.
   The flowchart execution will start with the default browser type.
6. To run a flowchart on a specific node, we can specify the node tag in prerequisites. For example, in the case of flowchart User Registration, BROWSER mode and windows10 node tag are specified in prerequisites.
   Flowchart User Registration will run only on the node which has the BROWSER mode and the windows10 tag.
infoNote: one can set the node tags in sahi.node.tags in sahi.properties
next Playback via Ant