As part of a form, you can set a question to be conditionally required based on the response to a prior question. For example, suppose you have an option set that users can pick from and one of those options is "Other". You can use Conditional Question Logic to ensure that, when "Other" is selected, you display a second question to gather follow-up information.
Navigate to the Question. In related records select either "Question Logic as Child" or "Question Logic as Parent"
Either place is fine to start from as the form is identical and asks for the same information.
Click "+ New Question Logic"
Fill in the Question Logic Form
- Name - A unique identifier for this Question Logic record. This is for internal use only and does not affect the behavior of the Question Logic.
- Type - The action to take when this Question Logic is triggered. There are three options:
- Conditionally Require - When this Question Logic is triggered, the Child Question will be required. Otherwise, the Child Question will be optional. Note that a question is not required when it is hidden.
- Conditionally Display - When this Question Logic is triggered, the Child Question will be displayed. Otherwise, the Child Question will be hidden. Note that a question is not required when it is hidden.
- Conditionally Enable - When this Question Logic is triggered, the Child Question will be enabled, allowing the user to edit the value in the Child Question. Otherwise, the Child Question will be disabled.
- Parent Question - Look up to the Question that will trigger the condition. If you start with the question and select Parent Logic this field should auto-populate.
- Answer - The answer that will trigger the logic. When the user answers the Parent Question, if their answer matches the value here, then this Question Logic will trigger. Note that this is not a look up. Instead, you must type the answer as it appears in an option set. If you are using a different question type, then only answers that exactly match this field will trigger the conditional logic.
- Child Question - Look up to the Question that will become required/displayed/enabled when this Question Logic triggers.
- Required Error Message - The message that will be displayed if a customer tries to skip the question if it is now required due to this Question Logic. This is only used if the Type is set to Conditionally Require
- Description - An optional field for any information you want to internally note about this Question Logic
Conditionally Display - How does it look on the portal?
In this example, we have set up a Parent Question named "What is your favorite color?" and a Child Question named "Please enter your favorite color". When selecting "Other" on the Parent Question, the Question Logic will trigger and display the Child Question on the Form. Note that this will happen in real time, and does not require the user to attempt to continue forward with the Form before it is displayed.
Note that in this scenario, we have set the Child Question as required on the Child Question record itself. A separate "Conditionally Require" Question Logic record is not needed to achieve this behavior.
Additionally, when the Child Question is not displayed, the Child Question is implicitly not required.
We can also set the Child Question to Not Required. This will still only display the question when the Question Logic triggers, but the Child Question will now display an indicator showing that the question is optional.
Conditionally Require - How does it look on the Portal?
In this example, we have set up a Parent Question named "How was your experience?" and a Child Question named "Additional Comments". When selecting "Bad" on the Parent Question, the Question Logic will trigger and make the Child Question be required on the Form. If the user attempts to continue without filling out the Child Question, an error message will display using the same text as the "Required Message".
Note that, in this example, we have set the Child Question to be not required. We could technically set the Child Question to be required, but this would result in the Conditionally Require record not doing anything useful, since the question would always be required regardless of the answer to the Parent Question.
Conditionally Enable - How does it look on the Portal?
In this example, we have set up a Parent Question named "Would you like to enter a date?" and a Child Question named "Custom Date". When selecting "Yes" on the Parent Question, the Question Logic will trigger and make the Child Question be enabled on the Form. When selecting "No", the Question Logic will trigger and make the Child Question be disabled on the Form.
Note that the Conditionally Enable logic does not automatically make the question also be required. In this example, the Child Question is still optional when enabled. If you want the Child Question to also be required when enabling it, you will need to add a Question Logic to Conditionally Require the Child Question.