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

Abnormal behavior of radio buttons, Grid Repeat (PegaSurvey)

SA-9451

Summary



In PegaSurvey 7.1 ML2 running on Pega 7.1.5, when the answer for the first question is Yes and the answer is No for second or fourth question, the answer of the first question automatically changes to No. When the radio button beside the options Yes or No is clicked, it behaves correctly. This issue occurs only when the questions having same set of answers are chosen.


Error Messages



Not Applicable

Steps to Reproduce

  1. In PegaSurvey 7.1 ML2, design four questions with the Radio Button control for the question mode:
    The answers for three questions, the first, second, and fourth questions in this case, have Yes or No display options with True or False as their values, respectively.
  2. Select the answer for the first question as Yes.
  3. Select an answer for the second or fourth question as No.
  4. Observe that the answer of the first question changes to No.
  5. Click the radio button beside the options, Yes or No.


Root Cause



A defect in Pegasystems' code or rules
Currently Pega does not generate unique IDs for user interface elements.

When a section with radio buttons is included in a Grid Repeat layout, the radio buttons in the inner section always generate the same ID for the "for" attribute when there are multiple rows in the grid. The ID should be unique for each row in the repeating Grid.

Resolution



Apply HFix-21897 for Pega 7.1.5 followed by HFix-22017 for PegaSUrvey 7.1 ML2.
Follow these steps:
  1. From the Designer Studio menu, click System > Tools > Update Manager > Install Hotfix.
  2. Install HFix-21897 to resolve the issue at Pega rules level in Pega 7.1.5.
  3. Restart the server by deleting the PegaRULES_Extract_Marker file in the temp folder.
  4. From the Designer Studio menu, click > Application > Distribution > Import and specify the file HFix-22017.jar to resolve the issue in PegaSurvey 7.1 ML2.
  5. Restart the server by deleting the PegaRULES_Extract_Marker file in the temp folder.
  6. In the user ruleset, Revalidate and Save the survey rules.
  7. Test the survey questions to verify that the problem is resolved.

Published May 3, 2018 - Updated December 2, 2021

Was this useful?

100% 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