Add a Router module and configure routes
The Router module allows you to branch your scenario into several routes, and process the data within each route differently. When a Router module receives a bundle, it forwards it to each connected route in the order the routes were attached to the Router module.
Routes are processed sequentially, not in parallel. A bundle is not sent to the next route until it has been completely processed by the previous route.
Access requirements
You must have the following access to use the functionality in this article:
| table 0-row-2 1-row-2 2-row-2 3-row-2 layout-auto html-authored no-header | |
|---|---|
| ÃÛ¶¹ÊÓƵ Workfront package | Any |
| ÃÛ¶¹ÊÓƵ Workfront license |
New: Standard Or Current: Work or higher |
| ÃÛ¶¹ÊÓƵ Workfront Fusion license** |
Current: No Workfront Fusion license requirement. Or Legacy: Any |
| Product |
New:
Or Current: Your organization must purchase ÃÛ¶¹ÊÓƵ Workfront Fusion. |
For more detail about the information in this table, see Access requirements in documentation.
For information on ÃÛ¶¹ÊÓƵ Workfront Fusion licenses, see ÃÛ¶¹ÊÓƵ Workfront Fusion licenses.
Add a Router module to a scenario
You must add a Router module before configuring routes.
-
Click the Scenarios tab in the left panel.
-
Select the scenario where you want to add a router.
-
Click anywhere on the scenario to enter the Scenario editor.
-
In the scenario editor, Click on the right handle of the module after which you want to add the router.
-
Select Flow Control > Router in the list of modules that displays.
Or
To insert the Router module between two modules, click on the wrench icon below the route connecting the two modules and select Add a router from the menu.
-
Add the first route to the router by clicking on the right handle of the router and adding a module, similar to adding any module.
-
To add another route, click the router module. A route appears. Add modules to this route as desired.
You can add as many routes as you want.
-
To verify the order of the routes, click the Auto-align icon
The routes are arranged in the order they execute. The top route executes first.
-
(Optional) To change route order, unlink the routes by right clicking on the path from the router and selecting Unlink, then dragging them to the router module in the desired order. The first route attached will be the first route to execute (the top route).
-
Continue to Add a filter to a route.
Add a filter to a route
You can put a filter on a route after the Router module to filter bundles. Only bundles that pass through the filter will be handled by the modules on the route.
If data passes the filter of more than one route, the data is handled by both routes. The top route handles the data first.
-
Click the Scenarios tab in the left panel.
-
Select the scenario where you want to add a filter.
-
Click anywhere on the scenario to enter the Scenario editor.
-
Click the wrench icon
-
Select Set up a filter.
-
In the label field of the panel that displays, add a label. This label displays in the scenario.
-
Configure filter conditions.
For more information, see Add a filter to a scenario.
-
Click OK to save the filter setup.
-
Continue to Configure a fallback route.
Configure a fallback route
The fallback route is the route that executes on any bundles that do not pass any filter to another route.
You can enable a fallback route in the filter panel.
-
Click the Scenarios tab in the left panel.
-
Select the scenario where you want to add a fallback route.
-
Click anywhere on the scenario to enter the Scenario editor.
-
Click the wrench icon
-
Select Set up a filter.
-
In the label field of the panel that displays, add a label. This label displays in the scenario.
-
Enable the fallback route checkbox.
-
Click OK to save the filter setup.
The Fallback route is marked with a different arrow in the Router module:
Example: if/else use case
A typical use case of the fallback route is to continue the flow with one route if the condition is met and with another route if it is not. as in the following steps:
In this example, the first route is configured with a filter. This represents the if component.
The second route is configured as a fallback route. This represents the else component.
