In this article, we concentrate on directing users along varied navigation paths based on their choices from a single-selection table. In such a table, users can select a single item from a list, allowing for diverse user interaction scenarios.
You can find screen templates with a single selection here
You can find screen templates with a single selection here
Table single selection
2-column single selection
Key points in using conditions for tables with single selection in the user segmentation process.
In tables with a single selection, when a user selects an item, you can immediately direct them along a specific pathway using outputs. This direct approach is effective for guiding users based on a single, clear choice.
In tables with a single selection, when a user selects an item, you can immediately direct them along a specific pathway using outputs. This direct approach is effective for guiding users based on a single, clear choice.
However, incorporating conditions in single selection scenarios can be particularly beneficial when you want to create a more complex user journey. For instance, if the choice of different items leads the user same paths right after screen, you can use conditions to segment the user experience several screens later. This allows for a more nuanced user journey, where initial selections influence the direction of the user's path in later stages
However, incorporating conditions in single selection scenarios can be particularly beneficial when you want to create a more complex user journey. For instance, if the choice of different items leads the user same paths right after screen, you can use conditions to segment the user experience several screens later. This allows for a more nuanced user journey, where initial selections influence the direction of the user's path in later stages
When implementing conditions for table single selections, you have the option to use operators like "==", "!=", and "in". Each of these operators serves a distinct purpose in segmenting users based on their selections. Here's a breakdown of when and how to use each operator:
When implementing conditions for table single selections, you have the option to use operators like "==", "!=", and "in". Each of these operators serves a distinct purpose in segmenting users based on their selections. Here's a breakdown of when and how to use each operator:
Segment users depending on their exact selected choices.
For instance: If they select Item1, they will navigate them to way1; if they select Item2, navigate them to way2; and if they make any other selection, navigate to way3.
To configure user navigation based on these specific selections, you will need to establish three distinct connections, two of them governed by a conditional statement using the "==" operator:
If users pick 'item1' from a list on screen1, they'll move to way1. This happens because there's a condition set: table single selection.list == item1.
Choosing 'item2' from the list on screen1 takes users to way2, following the condition: table single selection.list == item2.
If users select options that don't match the conditions for way1 or way3, they automatically go to screen 4. This includes selecting item 3 or item4.
Segment users based on their unselected choices.
For example: Users will navigate to way1 when they select any item except item1 .
To tailor the user journey based on these specific selection criteria, you'll need to establish two distinct connections, one of which utilizes the "!=" operator to create a conditional pathway:
If users select any items from screen 1 that do not equal item 1, they will be taken to way1. This is because of the condition set: table single selection.list != item1, item2. For example, selecting 'item2', 'item3', or 'item4' will all lead to screen2.
If users make a selection that doesn’t align with the first rule, they proceed to way2. In this scenario, selecting 'item1 from screen1 will take the user to way2, as this choice directly contradicts the '!= item1' rule
Segment users if they choose at least one item or combination from the list that you set.
For example, users can navigate to way1 when they select any item that includes one of the following: item1, item2, or item3. If they choose any item that doesn't include item 1, item 2, or item 3, they will navigate to way 2.
To configure this user journey based on these specific selection criteria, you will need to establish two distinct connections, one of which utilizes the "in" operator to create a conditional pathway:
From screen 1, if users select any item that matches one of the elements in the list [item1, item2, item3], they will be taken to way1. This is due to the condition:
screen1.list in [item1, item2, item3]. For example, selecting 'item1', 'item2', or 'item3' will lead to way1.If users choose an option that doesn’t align with the above condition, they are automatically redirected to way 2. This happens when they select options like 'item4' which don't match any specific element in the condition values.
Here are some key points to consider when adding conditions to your onboarding process:
Incorporating Conditions into Screen Sequences
Conditions can be set when you add the aforementioned screens in a sequence. For any transitions between these screens, you can specify corresponding Conditions to control the flow based on user actions or choices
Utilizing Multiple Conditions for a Single Transition:
It's possible to add multiple conditions to govern a single transition. Keep in mind that if multiple conditions are set, they operate in conjunction with each other, similar to an AND logical operator. For example, if you require a user to navigate to a specific screen, you could set Condition A (e.g.,
screen1.list == 'item1') and Condition B (e.g.,screen1.list == 'item3'). The transition will occur only if both these conditions are met, meaning the user must select both item1 and item3.
Managing User Pathway for Non-Matching Selections:
In instances where a user’s selection does not align with any of the established conditions, they will be redirected via a transition without conditions. If no such transitions are available, the fallback is to redirect them to the first programmed condition. This design ensures that there is always a clear, predefined path for the user, regardless of their selection, maintaining a fluid and user-friendly navigation experience.
Here is a comprehensive guide on how to add connections and integrate conditions into your onboarding process.