Include junctions in Bridge to route your workflow based on specific criteria.
USM Content
There are many kinds of junctions in Bridge, but all of them consist of two stages:
- Where the decision is made: This stage is based on input from another system or data stored elsewhere in the workflow. All the junction options describe the data analysis done in this stage.
- Where the possible routes are defined: This stage can consist of two or more states. Build your workflow to take one of multiple paths, depending on the results of the data analyzed in the first stage.
When creating a new junction, consider the following:
- Name at least three elements: One junction and two states.
- To specify additional pathways, drag the new states below the junction.
Conditional Junctions
Junctions analyze different kinds of data, depending on which junction module you use.
Conditional Junction modules help your workflows select which route to take. You can use them by applying logic to the data collected, which is pulled from an external data source during the workflow.
Refer to the Reference Data in the Workflow article for more information on referencing a pre-existing value.
Find Conditional Junction modules
Search for Conditional Junctions;
or
- Go to Utilities > Conditional Junctions.
True/False Junction modules
There are only two possible pathways for the workflow: true or false. All True/False modules create the junction as a group. Here's the list of the True/False Junction modules:
- More: Is a referenced value more than another one?
- Less: Is a referenced value less than another one?
- Equals: Does a referenced value equal another one?
- Match: Does a referenced string exactly match another one?
- Contain: Does a referenced string contain another string?
- Starts with: Does a referenced string start with another string?
- Ends with: Does a referenced string end with another string?
- Is empty: Does the referenced string exist?
Once you add the preferred Conditional Junction type, drag the states to the workflow builder. This will configure the module's success and failure branches.
For example, you could determine if a value meets a requirement by bringing in data from a sheet. Then, you can compare that data to the requirement specified in the More type of Conditional Junction.
Conditional junctions with more than two pathways
For a workflow with more than two pathways:
- Add Conditional Junction: Junction Match.
- Then, add the Junction itself. The Junction element matches the referenced data with its corresponding state (based on the state name). This element pushes the workflow to the necessary path.
For example, a user filled out a Smartsheet form identifying Product A, B, or C in a column. To specify the Smartsheet cell where the product type was selected, add the Junction Match element. It'll read the cell and tell the workflow which junction state names match that selected product.
You’ll also want to add a Fallback State, an alternate state for the workflow if none of the values entered in the cell match Product A, B, or C.
Configure the Junction Match
Junction Match is case-sensitive! Ensure the titles of your states are the same as your values.
- Open Junction Match.
- In the Junction field, add the data reference. In this example, the data reference is the product value gathered from the Get Row module.
- In the Fallback State field, put the name of your alternate state.
Use external tools to make junction decisions
You can also have external tools interact with Bridge to make junction decisions.
In this scenario, the workflow is getting a list from SharePoint. If there's a list, it goes down the State: List found path. If there's no existing user, it goes down the State: No list found path. Or, if there's no site found, it goes down the State: No site found path.
