Question
WillisTowerWatson
US
Last activity: 28 Oct 2022 16:11 EDT
Radio button referred twice with same property in a single section is not working as expected in 8.6.3
When the same property is refereed twice in a single section with radio button control .They are not working as expected .Radio button is selectable only once .
Similar kind of issue is mentioned in the below link only difference is dynamic layout instead of layout group.
https://collaborate.pega.com/question/radio-button-issue-case-dynamic-layout-group .
Did any one faced same issue ?
***Edited by Moderator Marije to add User Story, Support Article, Documentation tags***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Updated: 28 Oct 2022 16:11 EDT
Pegasystems Inc.
GB
The Enhancement Request US-92255 referenced in the PCC post you kindly referenced relates to a request in future versions to allow for Unique IDs for accessibility (ie where Radio buttons, checkboxes click will fire on some other harness element - For other controls, it will read incorrect labels )
When a same property is included in multiple sections and configured with 'run visibility condition on client', which causes generation of duplicate elements on dom with same name/id and this is the reason of the issue, you can see duplicate elements in dom.
Later Pega versions can deal with Auto Genrated Controls in Template and Non-Template mode which have been updated to have the unique id's.
The product cannot handle Duplicate IDs at layout level. Please open the Dev Tool F12 screen to verify this is occurring.
If you have several pairs of radio buttons with the same name in the dom, that will be causing the issue. Browser is unable to select the radio button while loading as there are more than 1 element with same name.
Can you confirm that if you uncheck the run visibility on client and also if you use the same property in different sections you do not experience the symptoms? See the steps outlined in the following support article.
The Enhancement Request US-92255 referenced in the PCC post you kindly referenced relates to a request in future versions to allow for Unique IDs for accessibility (ie where Radio buttons, checkboxes click will fire on some other harness element - For other controls, it will read incorrect labels )
When a same property is included in multiple sections and configured with 'run visibility condition on client', which causes generation of duplicate elements on dom with same name/id and this is the reason of the issue, you can see duplicate elements in dom.
Later Pega versions can deal with Auto Genrated Controls in Template and Non-Template mode which have been updated to have the unique id's.
The product cannot handle Duplicate IDs at layout level. Please open the Dev Tool F12 screen to verify this is occurring.
If you have several pairs of radio buttons with the same name in the dom, that will be causing the issue. Browser is unable to select the radio button while loading as there are more than 1 element with same name.
Can you confirm that if you uncheck the run visibility on client and also if you use the same property in different sections you do not experience the symptoms? See the steps outlined in the following support article.
Please see the various possible scenarios, and how to overcome them in this article "Radio buttons and check boxes in repeating grids misbehave"
WillisTowerWatson
US
@RashmithaM Any suggestions would be helpful ? Thanks In advance.
Accepted Solution
Updated: 28 Oct 2022 16:11 EDT
Pegasystems Inc.
GB
The Enhancement Request US-92255 referenced in the PCC post you kindly referenced relates to a request in future versions to allow for Unique IDs for accessibility (ie where Radio buttons, checkboxes click will fire on some other harness element - For other controls, it will read incorrect labels )
When a same property is included in multiple sections and configured with 'run visibility condition on client', which causes generation of duplicate elements on dom with same name/id and this is the reason of the issue, you can see duplicate elements in dom.
Later Pega versions can deal with Auto Genrated Controls in Template and Non-Template mode which have been updated to have the unique id's.
The product cannot handle Duplicate IDs at layout level. Please open the Dev Tool F12 screen to verify this is occurring.
If you have several pairs of radio buttons with the same name in the dom, that will be causing the issue. Browser is unable to select the radio button while loading as there are more than 1 element with same name.
Can you confirm that if you uncheck the run visibility on client and also if you use the same property in different sections you do not experience the symptoms? See the steps outlined in the following support article.
The Enhancement Request US-92255 referenced in the PCC post you kindly referenced relates to a request in future versions to allow for Unique IDs for accessibility (ie where Radio buttons, checkboxes click will fire on some other harness element - For other controls, it will read incorrect labels )
When a same property is included in multiple sections and configured with 'run visibility condition on client', which causes generation of duplicate elements on dom with same name/id and this is the reason of the issue, you can see duplicate elements in dom.
Later Pega versions can deal with Auto Genrated Controls in Template and Non-Template mode which have been updated to have the unique id's.
The product cannot handle Duplicate IDs at layout level. Please open the Dev Tool F12 screen to verify this is occurring.
If you have several pairs of radio buttons with the same name in the dom, that will be causing the issue. Browser is unable to select the radio button while loading as there are more than 1 element with same name.
Can you confirm that if you uncheck the run visibility on client and also if you use the same property in different sections you do not experience the symptoms? See the steps outlined in the following support article.
Please see the various possible scenarios, and how to overcome them in this article "Radio buttons and check boxes in repeating grids misbehave"
-
Riya Rana Radheesh S
WillisTowerWatson
US
@MarijeSchillern Thank you Marije . It worked when I unchecked run visibility on client . Also, I was able to refer in two different sections and did not experience this issue. But , I have a concern if we are not using run visibility on client ,we need to refresh the section always whenever we want to display other layout based on some conditions. Please do let me know if we have any other alternative other than refresh the section.
Pegasystems Inc.
GB
@RashmithaM I have requested internally that a product SME respond to you in case they have any suggestions for you.
WillisTowerWatson
US
@MarijeSchillern Thank you .
ARETEANS TECHNOLOGY SOLUTIONS PRIVATE LIMITED
IN
Its working fine for me too! Thanks.
-
Marije Schillern
Evoke Technologies
US
@RashmithaM Can u try to call the other radio button to new section & try to call the new section in main section.
Hope you got it!