We’ve introduced Routers so users can define custom logic and control mappings for inputs and outputs of their Workflow tasks! Routers also allow users to create more efficient and accurate workflows by eliminating manual adjustments.
Routers are currently best suited to support the following flowchart use-cases:
- Core Variants: When a flowchart is configured to have several discrete “paths” that users select based on specific criteria – such as sample type or sequencing method.
- Assay Panels: When a requester has a set of samples that need to undergo a series of analytical tests, and each sample may require a different subset of tests.
Once the Task Schemas and Transitions tabs of the flowchart configuration section in your flowchart task schema have been completed, you can add Routers to the Flowchart Template.
Add Routers in Flowchart Editor
Adding a Router:
- Click on the pencil icon of your template flowchart to open the modal.
- Drag and drop task schemas from the side panel onto the canvas.
- Drag a diamond-shaped router node from the side panel onto the canvas + create connections between task schema nodes.
- Open the configuration modal for the router node to set up rules for each connected edge:
- The router editor is comprised of making the below selections:
- Determining which field will be mapped (ie. assay type) between source and target tasks
- Operator conditions (ie. “is” or “is not”)
- Lookup value(s) (ie. dropdown options from mapped field)
- Routing path (target task)
- Note: At this time, routers only support mapping field(s) from a source task to target task via a dropdown field.
- Optional: Edit the name(s) of the router nodes and results.
- Create Rules for all target tasks that are outgoing edges from the router + for “All other cases”
- Select the appropriate operator and value for each rule based on the lookup.
- Submit changes to the template flowchart, and Submit changes to the flowchart configuration section!
The router node must meet the following criteria:
- It has exactly 1 incoming edge
- It has at least 2 outgoing edges
- There is a corresponding schema mapper for each edge between 2 task nodes
- The router node is not connected to another router node
- A task schema node only has 1 incoming router node
- A single outgoing edge cannot have more than 1 rule applied
- One edge must be designated as “in all other cases”