Limited support

 

This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments. Click here to view the documentation for the current version.

Building conditional questionnaires

Catalog administrators and internal service suppliers apply conditions in a questionnaire, so that questions displayed in a service request are based on the user's responses to previous questions.

Form element types for which conditional questionnaires are available

You can add conditions to form elements that can be configured to return multiple responses. Use one or more values in these responses or use free text responses to make a decision to display additional questionnaires to your users. Use the Map to Form or Map to Dataset option to get, and use dynamic responses for displaying questions.

The following table shows the form element types and options available for each type.

Form Element TypeDynamic responsesFixed responses
Map to FormMap to DatasetAdd Value
Checkbox

yes

yes

yes

Dropdown

yes

yes

yes

Multiselect Dropdown

yes

yes

yes

Radio Buttons

yes

yes

yes

Toggle (Yes/No)

Not applicable

Not applicableFixed values (Yes/No)
Lookup

yes

Not applicableNot applicable

To add conditions to questions

Add conditions to questions with fixed or dynamic responses. Use the responses from questions to decide on subsequent questions.

Note

Do not delete a question or value that is used to determine if another question will be displayed.

  1. Click New question or use a question that returns a response. For more information, see Creating selection menus for question responses.
  2. Click New conditional branch to add the conditional question.
  3. Click the + button to add a condition that uses the response to another question to determine if the question within the conditional branch is displayed.

    Select a question from the Insert question drop-down list. You can select a question that uses Form Element Types with fixed or dynamic responses. You can also use free text to provide a response for validating the condition.

    Tip

    Use the available expressions to build questionnaires that evaluate multiple conditions. For example, you can provide the option of an additional monitor to a user only if they have a laptop and a docking station.

    For more information on creating questionnaires that use responses from external asset forms, see Creating a questionnaire with answers prepopulated from an external asset form.

  4. Select the question that will be displayed for the condition in another question.

    Note

    You must create conditional questions on the same page.

Example: Create a questionnaire that allows laptop users to request an external monitor 

Step 1: Create a question that allows users to select their computer type.

Click New question, and use the following details in the Question Designer.

FieldValue
Form Element TypeDropdown
LabelSelect your computer type
Question Values > Add ValueLaptop
Question Values > Add ValueDesktop

Step 2: Create a question that allows users to request an external monitor.

Click New question, and use the following details in the Question Designer.

FieldValue
Form Element TypeToggle (Yes/No)
LabelDo you need an external monitor?

Step 3: Create a conditional branch that allows users to request an external monitor only if they are using a laptop.

  1. Click New conditional branch.
  2. Click the + button. Click Insert question  > Computer type. Use the default is condition, and select Laptop from the drop-down list. Alternatively, you can use free text to provide a response for validating the condition.

  3. The second question (Do you need an external monitor?) you created will be available in the User Generated Questions list on the left. Drag and drop this question into the conditional branch you just created. This question will be displayed only if the user selects Laptop as the Computer type.

Step 4: Save and publish the questionnaire as a part your service.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments