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
| table 0-row-2 1-row-2 2-row-2 layout-auto html-authored no-header | |
|---|---|
| Adobe Workfront package |
Any Adobe Workfront Workflow package and any Adobe Workfront Automation and Integration package Workfront Ultimate Workfront Prime and Select packages, with an additional purchase of Workfront Fusion. |
| Adobe Workfront licenses |
Standard Work or higher |
| Product | If your organization has a Select or Prime Workfront package that does not include Workfront Automation and Integration, your organization must purchase Adobe Workfront Fusion. |
For more detail about the information in this table, see Access requirements in documentation.
Add a Router module to a scenario
You must add a Router module before configuring routes.
Add a Router module to a scenario in the new experience (Recommended)
-
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.
-
Hover over the right edge of the module after which you want to add the router, then click Add another module when it appears. In the list that opens, select the Built-in category, then select Flow Control > Router.
Or
To insert the Router module between two modules, right-click the path connecting the two modules, then select Add a router.
-
Add the first route to the router by hovering over the right edge 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, check the label for each route. Route 1 executes first, then Route 2, and so on.
Or
Click the Auto-align icon
The routes are arranged in the order they execute. The top route executes first.
-
(Optional) To change route order, right-click the Router module and select Order routes. Drag and drop the routes in the order you want them to execute in. Routes are marked by the first module that follows the router (the first module of the route).
-
(Optional) To disable a route, right-click the path that leads from the router to that route, and select Disable route.
Disabled routes display gray dots leading from the router to the first module on the route, and show a the disabled route icon
-
(Optional and conditional) To enable a disabled route, click the disabled route icon
-
Continue to Add a filter to a route in the new experience.
Add a Router module to a scenario in the classic experience
-
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, then 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, check the label for each route. Route 1 executes first, then Route 2, and so on.
Or
Click the Auto-align icon
The routes are arranged in the order they execute. The top route executes first.
-
(Optional) To change route order, right click on the Router module and select Order routes Drag and drop the routes in the order you want them to execute in. Routes are marked by the first module that follows the router (the first module of the route).
-
(Optional) To disable a route, right click on the dots that lead from the router to that route, and select Disable route.
Disabled routes display gray dots leading from the router to the first module on the route, and show a the disabled route icon
-
(Optional and conditional) To enable a disabled route, click the disabled route icon
-
Continue to Add a filter to a route in the classic experience.
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.
Routers with filters display the filter icon
Add a filter to a route in the new experience (Recommended)
-
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.
-
Left-click the path where you want to set a filter. This is the path between the router module and the first module of the route.
The Set up a filter window opens directly.
-
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.
-
(Conditional) If the filter name is too long to fit in the label, hover over the label to display the entire name.
-
Continue to Configure a fallback route in the new experience.
Add a filter to a route in the classic experience
-
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.
-
(Conditional) If the filter name is too long to fit in the label, hover over the label to display the entire name.
-
Continue to Configure a fallback route in the classic experience.
Configure a fallback route
The fallback route is the route that executes on any bundles that do not pass any filter to another route.
Fallback routes display “Fallback” on the label.
You can enable a fallback route in the filter panel.
Configure a fallback route in the new experience (Recommended)
-
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.
-
Left-click the path where you want to set a filter. This is the path between the router module and the first module of the route.
The Set up a filter window opens directly.
-
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’s label displays Fallback in green.
Configure a fallback route in the classic experience
-
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:
Fold a router
In the new experience, you can fold a router to temporarily hide its routes. This is useful in large scenarios.
- Open the scenario in the scenario editor, in edit mode.
- Right click on the router that you want to fold, then select Fold routes
The folded router shows how many routes and modules are hidden, including the severity of any hidden warnings or errors.
Folding a router does not remove or disable anything. Search, validation, Live Trail, and execution history automatically expand a folded router when they need to show a module that is inside it.
The folded state is saved with the scenario and works with undo and redo. When you review a scenario execution, the complete scenario always displays.
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.
