Skip to main content

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.

Support Article

Existing Simple Question rule with Rich text is not working

SA-32991

Summary



Existing Simple Question rule(before PegaSurvey7.2.2) with Question layout type as 'Rich text' is not working after upgrade.
When user tries to 'revalidate & save' the rule, user could see the error 'Display text cannot be left blank'.on UI and clear selection is not working and options are appearing with alignment issues.


Error Messages



Display text cannot be left blank.


Steps to Reproduce

  1. Create Simple Question rule with Question layout as 'Rich text' and provide some value in the field below in PegaSurvey 7.1 version or earlier release.
  2. Link it appropriate Question Page, etc. So that we can see it on UI.
  3. Check, UI is proper and 'clear selection' link works.
  4. Upgrade it to Pega Survey 7.2.2 version.
  5. Check UI is not proper. and 'clear selection' link doesn't work.
  6. Try to 'revalidate & save' the rule, we could see the error 'Display text cannot be left blank'.


Root Cause

The user is not able to validate and save the questions when upgrading from Pega Survey 7.1 version to 7.2.2​ version.

QuestionText is missing at the time of upgrade because the property pointing to QuestionText of Rule-PegaQ-Question got changed. So making changes in OpenDefaults of Rule-PegaQ-Question activity for backward compatibility would resolve the issue.



Resolution



Applying HFix-31661.

Published February 7, 2017 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us