High Score node reference
You can send visitors down a different path based on their highest or lowest score. See how to choose the scores, compare variables, and handle ties.
High Score compares flow scores or stored numeric variables and sends each visitor down one path. The highest value wins by default. You can choose the lowest value instead without changing any of the visitor's values.
When to use it
Use this node when several answers contribute points toward a recommendation, or when you want to compare numeric variables. Award points through question answers or Set Data before the visitor reaches this node.
High Score appears in the palette when the current flow has at least two score names, or your project's flows have at least two variable names.
Settings
When multiple scores exist, a new node starts in Flow Scores mode with a route for each score. Otherwise, the editor can start in Variables mode with no routes. The lowest-value setting is off by default.
| If you'd like to… | Setting |
|---|---|
| Compare scores used in this flow | Flow Scores selects names from the current flow. |
| Compare stored variables | Variables selects names assigned across your project's flows. It reads their stored values that haven't expired. |
| Choose the smallest value | Turn on Lowest score wins, or Lowest value wins in variable mode. |
| Choose a candidate for a path | Select its name in the route's row. Names already used by another row aren't offered again. |
| Decide which path wins a tie | Drag the rows into priority order. The first tied row wins. |
| Add a path | Choose Add another score, or Add another variable in variable mode. |
| Remove a path | Remove its route and confirm. This also removes the nested nodes in that path. |
Switching modes
Switching modes replaces your branches. Once a route has a selected name, Switch Mode? asks for confirmation, even if the path is empty. If it contains nested steps, the dialog also warns that those nodes will be removed. Switch applies the change. Cancel keeps your current routes.
Switching to scores adds routes for the current flow's scores. Switching to variables starts with an empty list, so add and select each variable route before leaving the editor. In score mode, the editor adds routes for newly discovered score names when the flow's available scores change.
How visitors move through it
Only the candidate names you've selected take part. The visitor follows the path with the highest value, or the lowest if you've enabled that setting. If values tie, the first tied row wins.
Both modes read the available scores and variables that haven't expired. A numeric string such as "8" is compared as the number 8. A variable with the same name as a score takes precedence over that score. Unrelated variables aren't included.
Missing, expired, null, and whitespace-only variable values don't supply a numeric candidate. If only one candidate has a value, that candidate wins. A missing value isn't zero. If every candidate is absent, or a participating value is nonnumeric, the first named route wins.
For example, suppose your rows are ordered planning, then collaboration:
| Values before the node | Highest wins | Lowest wins |
|---|---|---|
| planning 8, collaboration 2 | planning | collaboration |
| planning 2, collaboration 2 | planning | planning |
| planning absent, collaboration 2 | collaboration | collaboration |
| Both absent | planning | planning |
| planning 0, collaboration -3 | planning | collaboration |
Things to know
- Set an initial value for every candidate when zero matters to your comparison. An absent candidate won't be treated as zero.
- Use numbers, not labels such as
planningandcollaboration, as the values you compare. Variable conditions can match text or check whether a value is set. - The editor removes old Default rows. If unanswered visitors need a different path, put a condition before High Score rather than relying on the first-row fallback.
- The chart icon beside each route doesn't currently open a score editor here. Assign points in the question or a Set Data node instead.
For a complete scoring setup and its test cases, see score and route a quiz.