Skip to main content

 –

Conditionally displaying a question page in a questionnaire

Suggest edit Updated on November 26, 2021

Define conditions to ensure that your questionnaire displays related questions that are relevant to a given scenario, based on the context of the questionnaire participant. For example, in an onboarding application, the questionnaire displays questions about preferred office accommodations only if the employee does not work remotely.

  1. Navigate to the questionnaire:
    ChoicesActions
    Open the questionnaire in App Studio
    1. In the navigation pane of App Studio, click Case types.
    2. In the list of case types, open a case type of the Questionnaire type that you want to edit.
    Open the questionnaire in Dev Studio
    1. In the header of Dev Studio, click ConfigureCase ManagementQuestionnaire.
    2. Click the questionnaire that you want to edit.
  2. Click the question page for which you want to configure visibility conditions.
  3. In the Page settings pane, in the Visibility conditions section, click the Properties icon.
  4. In the Conditions dialog box, define a condition by providing a value to compare at run time, a comparator, and a value to compare against the first value.For example: To display the question page only to customers who stay at a hotel for five days or more, enter Duration is greater than or equal to 5.
  5. Optional: To add more conditions, click Add a row.
  6. If you create multiple conditions, define whether a case needs to meet all or any conditions by selecting either and or or between the rows.
  7. Click OK.
  8. Click Save.
Result: At run time, the question page is displayed only if the visibility conditions evaluate to true.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us