We are using a section as a common component by calling them through different page context. The context varies through the page group as below. In the portal we are calling the same section multiple times with different page context altogether. When we directly click on the check box the value is getting set correctly. Instead if we click on the label it actually changes the value of that check box in all that section references.
Section name: SampleSection
Page Group name: SamplePageGroup
Is it a bug? or is there any solution for this?
***Moderator Edit: Vidyaranjan | Updated SR details and tagged srcreated***
I did some local testing but could not produce this behavior. Can you please share some screenshots showing how you have the checkbox and label configured, and indicating what you're clicking on at runtime?
Could you please also let us know what version of the Pega Platform you are using?
PFA for the UI screenshot. In that, the marked set of check boxes are referred multiple times. In the screenshot, i have captured where they are referred twice. We have the check box properties in our data class and we have created a section(InputOutputMethod) with the four check boxes in the data class itself. Now we are calling the section(InputOutputMethod) from our work class main section using page contexts pyWorkPage.Product(ACHOrigination) and pyWorkPage.Product(InternationalPymt) where the page group property .Product is of type that data class. Now as in the screenshot, if we click on the Treasury Edge option lable under the International Payments the same selected Treasury Edge option under ACH Origination will get blanked out.
Thank you for the screenshot, and the clarified description of how the problem presents itself. I can produce a somewhat similar behavior in 7.2.1, but it's different enough from what you've described that I'm not sure if its really the same thing. If you can provide some screenshots of the design time view, and let us know what version you're on, that could be helpful.
If you're on 7.2.2, you may want to look into the hotfix that Carissa mentioned.