Bullet point lists can be incredibly pleasing to the eye of the reader. They help condense information and appear easier to tackle when they entail tasks. This is especially true when bullet point lists are dynamic in size so as not to present any unnecessary information. Learn how to take your module to the next level by incorporating context-sensitive bullet point lists.
In this example, we are looking at a GDPR Compliance Checker Module: The user fills out a questionnaire and receives a set of recommendations based on their selections. This set of recommendations is designed in the form of a context-sensitive bullet point list.
- Create and name an empty Text Block Value Node (e.g. "Recommendations") that will later hold your bullet point list. Then create your questionnaire using Input Nodes.
- For every additional bullet point on your list, place a Text Block Value Node after every Input Node. In the title field that reads "New Value", start typing out the name of your first Text Block Value (here "Recommendations"). An option to update your current Text Block Value will appear and link the Nodes together. Repeat the process for each question.
- Select the first updated Text Block Value Node. Activate the bullet list button and type out your first bullet point. Select the second updated Text Block Value and prior to typing out your second bullet point, reference the above Text Block values by typing out "@" followed by the name of your Text Block value (e.g. "Recommendations"). Repeat the process for each question.
- To turn this bullet point list into a context-sensitive bullet point list (meaning only applicable recommendations will be shown in the list), you will need to include Conditional Logic. The logic tree needs an additional branch after each question to ensure that user input will either trigger a new bullet point on your list or just skip to the next Input Node for a new question. Place a Transition leading from one Input Node to the following. Repeat the process and set conditions accordingly for each question.
In our example: If the organization does not have a DPO, the condition for the Transition leading from the Input Node "DPO" to the Text Block Value Node "Recommendations" is set to "DPO = No". Every other user input – "else" will skip over the Text Block Value, therefore not triggering a new bullet point on the list.
- Finally, reference the Text Block Value in your Result, a Document, or an Email action by typing out "@" followed by the name of your Text Block Value Node (here @Recommendations).
The content of the Result Node includes a reference to the updated Text Block Value Nodes above, as well as an additional download link for a document that holds the context-sensitive bullet point list.
- Preview your Module.
This is how the result page is displayed to the user in the published end-user interface.