Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Displaying a warning in a survey

Updated on April 5, 2022

Use a warning message to encourage survey participants to provide complete answers.

  1. In the header of Dev Studio, click ConfigureCase ManagementSurvey.
  2. On the Questions tab, click a question.
  3. Expand the Warnings section.
  4. Define the conditions that control whether the warning is displayed.

    The types of conditions that you can use are based on the type of question.

    • To use a when condition:

      Use this approach when users complete your survey online.

      1. In the Visibility list, select Condition (when rule).

      2. In the Warning when field, press the Down Arrow key and select the name of a when condition that evaluates property values in the survey.

    • To use a Boolean expression:

      Use this approach users complete your survey offline.

      1. In the Visibility list, select Condition (expression).

      2. In the Warning expression field, enter a string expression that evaluates property values in the survey.

    • To use a combination of when conditions and Boolean expressions:

      1. In the Visibility list, select Condition (expression).

      2. Click the Condition builder icon to open the Visible when dialog box.

      3. Enter values in the fields based on the type of conditions and property values to evaluate at run time.

      4. Click Save changes to close the Visible when dialog box.

  5. Click Save.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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