Conditional Logic allows forms to adapt dynamically based on user inputs, offering a personalized and intuitive experience. By presenting or hiding objects based on specific criteria, Conditional Logic streamlines the form-flow process, guiding users seamlessly through each step.
This article will offer insight into some of the best practices that Workflow Designers can employ when implementing business intelligence within the TrueContext platform. Whether you are a seasoned or novice designer, mastering these principles will empower you to create forms that not only capture data but also foster positive user interactions.
From the mobile user's perspective, the action of completing a page, section or question could contain the following:
Questions set as:
Hidden or shown (visible/ not visible)
Is read-only / not read-only
Is required / not required
Is set to [ a certain value] / is cleared [of all values] / is reset
Pages and sections set as:
Ignored or unignored (meaning existing or non-existent in submissions)
Understanding this, let us look at some considerations to make when developing Conditional Logic rules:
Visualize your workflow: It is important to step back and analyze what actions you want to happen when your conditions are met. Have a clear vision of the scenarios your end-user will experience and map these out before you start creating your Conditional Logic rules.
Labelling: When creating Conditional Logic rules, clearly label your rule names and rule descriptions as you could have similar rules and want to limit mistakes / confusion. Standardized labels allow for utilizing Data Destinations across multiple forms with minimal mapping efforts.
Required Questions: Setting questions, connected to your Conditional Logic rules, as "Required" may assist you to land your desired outcome.
Intuitive form flow: If your field technicians are getting stuck on the way the questions are being asked, and what triggers make the Conditional Logic happen, it is worth revisiting how they are set up. Look at simplifying the wording of your questions, avoiding double negatives, and use natural language.
Watch out for Overwriting: Look out for Conditional Logic rules that overwrite the action of another rule. Let's take a look at this example: RULE 1: IF Q1 = 5 THEN Q3 is Visible ELSE Q3 is Not Visible RULE 2: IF Q2 <3 THEN Q3 is Not Visible ELSE Q3 is Visible In the example above, while each rule is perfectly valid on its own, Q3 will have likely behave strangely, as the user fills out Q1 and Q2. If Q1 does equal 5, and Q2 is indeed less than 3, the visibility of Q3 will depend on which question the mobile user last interacted with -- so if they last modified Q1 that is the rule which will control the behaviour. It would be best to rewrite this as a single rule: IF (Q1 = 5 AND Q2 ≥ 3)
…and finally
Test! Test! Test!: To make sure your Conditional Logic rules work as intended in the field, test them thoroughly before you deploy the form. Our platform is extremely dynamic, so make sure to test the workflow under a variety of conditions to validate the field user experience. This also includes testing with different operating systems, if you are running multiple OS devices deploying the same form.
Ultimately, Conditional Logic forms part of the brain behind the form. It is meant to work as a human would in the background, guiding the user through the experience of filling out the form. The more intuitive you build your Conditional Logic rules, the less opportunity there is for confusion, and you will give yourself the best chance to get clean data from your submissions.
Full documentation covering the Conditional Logic feature, including how to create and manage Conditional Logic rules in your forms and explaining the different Operators and Actions available to you, is available in our product documentation here: https://docs.truecontext.com/1374411/Content/LandingPages/ConditionalLogic.htm
Additionally, you can take the following learning paths in our free, self-paced, TrueContext University:
L1: Conditional Logic - https://university.truecontext.com/training/afb65924-eaf1-11ed-ae30-02d47b69d3fd/overview
L2: Conditional Logic - https://university.truecontext.com/training/0e211390-4e6c-11ee-b36a-0213f4967ee3/overview
#TechTalkSuccess #BestPractice
Reminder: Content posted to our Community is public content. Please be careful not to post Intellectual Property that you do not have permission to share. For more information please refer to our Terms Of Use.