Add Path

Introduction

Feature Overview

The Add Path node enables you to can add multiple paths in an automation, so Automations Pro will perform actions according to different conditions. This type of node support orderly run (run paths in a sequential order), parallel run (run multiple paths simultaneously), and conditional run (run paths based on conditions you set).

Scenario

Path Nodes are applicable in the workflow scenarios that require different actions according to different conditions or situations.

Preview

Take car renting as an example, after submitting the car returning application, if the amount of oil is less than 20 in the car, it will initiate the refueling process. If the car has malfunctions, it will initiate repairing process. Other situations are all seen as successful returning. In the picture below, the car has both the problems of low fuel and malfunction, so it will initiate refueling and repairing processes at the same time.

How to Set

This section takes the scenario of car renting as an example to explain how to use Path Nodes.

Adding a Path

Add an Add path node after the existing nodes. Then two paths will appear:

Path one: The path on the left consists of Add path nodes and action nodes. In the path, Automations Pro performs certain actions under certain conditions.

Other path: The path on the right only consists of action nodes. In the path, Automations Pro performs certain actions when no conditions are met.

For example, to break down the tasks in the car returning scenario, you can achieve them by adding three paths in Automation Pro.

When you add an Add path node, there will be only two paths. Therefore you need to add two more paths.

Setting the Path Rules

When Automations Pro run at a Add path node, it will first check the path conditions and then run the corresponding path when certain condition is met. If there are multiple paths that meet the conditions, you need to set whether to allow Automations Pro to run multiple paths at the same time according to your actual business:

For example, when you return the car, you may encounter the situations like low fuel and malfunctions, and you need to allow it to initiate refueling and repairing processes at the same time, thus select Take all Paths that Meet Conditions.

Setting Path Conditions

Path Nodes are used to control the execution direction of Automation Pro, only allow it to take the path that meet the conditions and execute the node operations at the paths.

Click Add Condition, the settings required are as follows:

l Relationships between multiple conditions: when there are multiple path conditions, you can select to meet all of or any of the conditions:

n all of: the relationship between multiple path conditions is "and", only available to query the records that meet all of the conditions

n any of: the relationship between multiple path conditions is "or", available to query the records that meet any of the conditions

l Fields at the preceding nodes: Select fields stored at the preceding nodes in the current Automation Pro or part of the system fields (Created User, Created Time, Updated Time, and Workflow Status).

l Filter relationships: Set different filter relationships based on the types of fields in the target form, such as equals, does not equal, contains, does not contain, is empty, and is not empty.

l Filter value: You can select Field Value at Nodes, Custom or Empty. If you select Custom, you need to enter the value manually.

For example, in the scenario of car returning, task one is "when the amount of oil in the car is less than 20, initiate the refueling process", then settings of the path conditions on corresponding paths are shown in the above picture.

Note:

1. Different types of fields in the target form are able to set different filter relationships and filter value. For details, see Illustrations for Filter Value.

2. The preceding nodes that are available to quote the field value include: Query Record/Records, Add Record, Calculating Node, and Plugin Node. When trigger method is Scheduled Trigger > Custom Time, it cannot quote the field value of Trigger Node to assign value.

3. Some fields in the target form are unfeasible to set path conditions, including: Subform Fields, Divider, Query Data, Select Data, Button, Current Node, and Current Approver.

Path Operations

Adding Paths

Click "+" > New Path and you can add a new path before the other paths at the same level, as shown in the following picture.

Deleting Paths

1. Delete single node

If you need to delete the execution nodes on a path other than Path Condition Nodes, hover your mouse over the corresponding node and click the Delete button.

2. Delete single path

If you need to delete a single path, you can just delete the Path Condition Nodes on that path. While deleting Path Condition Nodes, it will delete all the execution nodes on that path in cascade.

3. Delete whole path

If you need to delete the whole path, just delete the Path Node. While deleting the Path Node, it will delete all the paths and execution nodes on the them.

Note：

While deleting path condition nodes, it will delete all the execution nodes on that path in cascade.

Adjusting Path Order

1. Adjust the order of execution nodes on the path

For execution nodes on a path other than Path Condition Nodes, you can adjust their order and position to any place in the workflow by dragging, such as the same path, other paths at the same level, subordinate paths and out of paths.

2. Adjust the order of the whole path

Drag Path Condition Nodes directly to adjust the order of paths that the nodes are on.

Copy/paste Paths

For similar and complicated paths, you can achieve rapid configuration of paths by copying, pasting and then update them.

1. If you need to copy a path, just copy the Path Condition Nodes on that path.

2. Click "+" > Paste Path to paste the copied whole path before other paths at the same level.

Notes

1. Paths can be nested for 10 layers in maximum.

2. Path Condition Nodes are only used in condition judgement instead of data storage, so they cannot be called by the following execution nodes.

3. While executing a path, it will execute every node by order from the top to the bottom. Once the node is successfully executed, the result of the former nodes will not be affected even if the following nodes are failed to execute.

4. While multiple paths are being executed at the same time, the paths will be independent and will not affect each other. If path one and path two are executed at the same time, when a node on path one is failed to execute, it will not affect the continuous execution of path two. Automation Pro will stop operating until the execution of path two is completed.