Note: This is a limited-release feature. It can currently be added to your forms by our Professional Services team. Please contact your ProntoForms account manager for more information.
Every workday involves making thousands of decisions based on past information and current conditions. This is conditional logic. Applying it to mobile forms adds intelligent automation to form, thereby speeding up any workflow
The basis of conditional logic is in this statement: "If This, Then That." You create a task or action that happens when certain conditions are true. Set up the condition, choose the action that occurs.
We see this all the time in paper forms: "If NO, then add detail below." Conditional logic improves the speed and quality of data collection in the field by guiding the mobile user through a workflow relevant to the job's context: they require less training and spend less time filling out forms.
Conditional logic only functions on V2 forms, meaning they must be built by ProntoForms at this time.
As mentioned above, the basis for conditional logic is "If This, Then That." If This is true, then That action will happen. This is a conditional statement. Using the example of a site inspection form:
If/Else (and elseif) statements allow you to define what happens when the IF statement is not true.
Else If the room being inspected equals the washroom, then show the "washroom" section, hide the "common area" section, and hide the "warehouse" section.
Else If the room being inspected equals the warehouse, then show the "warehouse" section, hide the "common area" section, and hide the "washroom" section.
Else, hide the "common room" section, hide the "washroom" section, and hide the "warehouse" section.
What conditions can I use in Conditional Logic?
The condition in a conditional logic statement is the part that is true or false. Using our earlier example:
If there is inadequate edge protection, then we need to enter more details.
The condition here is "inadequate edge protection," and the resulting action is "enter more details." If the trigger is true, then the action happens. You can use a number of different operators, including but not limited to:
Equals (=): "If this answer equals exactly this value, then these actions will happen." This can be a number, a particular sentence or word, or many other user-entered data types.
Inequalities (>, <, ≥, ≤): "If this answer is more (or less) than this value, then these actions will happen." This works best with numbers and dates. For example, an inspection form might have a numeric question to rate the condition of a site; if that numeric value were under a certain number (i.e., a poor rating), it could trigger a text box to add details. Mobile forms also support less than or equal to, and greater than or equal to.
Contains: "If any part of this answer has this in it, then these actions will happen." This can be another question, or a key phrase, or a certain set of numbers (such as an address or a part number); this could be used to fill other questions with relevant information on the part number mentioned in a larger string of data.
This is a brief overview of the actions currently supported. Actions dictate what happens when a condition is true. In this product's case, actions can hide a page, make a question required or not required, and other actions - essentially, they change the user's path through the form.
Currently, mobile forms support the following actions:
- Showing or hiding questions, sections, or pages.
- Setting questions to Required/Not Required.
- Setting questions to Read Only/Not Read Only.
- Setting or clearing the value for questions.
These actions can:
- make mobile forms easier and faster for end users to fill by adapting the form to be relevant to their context or job at hand.
- allow form builders to build "smart" forms that ensure end users collect all the information required in a specific workflow.