Overview: Branching and Combining Tasks

Tasks can be linked and branched to create more efficient and flexible applications. Branches are usually added at test time, while you can link tasks to existing tasks when you start recording.

Adding a branch to your task lets you deliver multiple outputs by using different task inputs. By using a different input value than the task is expecting, the task will follow a different path.

You can also supply an alternate navigation path to your task by inserting a new step destination. Use this feature to bypass a recorded screen, in essence creating a "shortcut" for your task. For more information, see Adding New Task Step Destinations.

Creating Parent Tasks

Creating parent tasks lets you join tasks together from designated task end points. By linking tasks together, the existing task becomes the "parent" of the new task. When you start recording, Task Builder automatically navigates to the endpoint of the parent task. Using parent tasks, you can record a task once and then use the task as the login for other tasks, without having to re-record it each time.

Any task that exists in your project is available to become a parent to other tasks. A task parent is compatible with its connected task if, and only if, the screen referred to by the task parent's terminal state (endpoint) is the same screen as that referred to by the connected task's initial state.

Once a task has been given parents, it cannot be "orphaned" or stranded. This is true both when you create a task and when you run the task. While you can create a task without parents (one that navigates from its initial screen back to its initial screen), you cannot remove all task parents from a task.

Navigating tasks with multiple parents

Since a task can be a parent to multiple other tasks, and a task can have multiple parents, there can be many different navigation paths available to you. During navigation, if your task has multiple parents, you can choose a particular parent task, thus ensuring a particular navigation path. This is important as different navigation paths can produce different task input values.

Recognizing a Task that Branches

In most cases, the recognition rules generated by Task Builder are sufficient for identifying task steps and running a task that contains branches. However, occasionally, it might be necessary for you to manually edit the recognition rule. If, when testing your task, you do not see the Unrecorded Screen dialog box or the expected step output, verify that each recognition rule is distinct, make any needed modifications, and test the task again.

Related Topics
Bullet Designing Tasks, Overview
Bullet Adding Branches to Tasks
Bullet Linking Tasks
Bullet Adding New Task Step Destinations