Question
Capgemini India PVT Ltd
AU
Last activity: 4 Aug 2025 0:24 EDT
Page group property on clipboard appearing as pagegroup.pxResults
Hi All,
In our Pega application which is running on PEGA platform 8.8.5, we are using a Page Group property to store key-value structured data. The values are being appended correctly in all lower environments (Dev, QA, UAT), but in Production, we’re noticing that the clipboard sometimes shows the page name as "PageGroup.pxResults".
This is unusual since pxResults is typically used with Page List properties, not Page Groups. We’ve confirmed that the property is defined as a Page Group, and our implementation does not include any reference to this property as a list anywhere in the application.
Has anyone encountered this kind of clipboard behavior before? What could cause a Page Group to display pxResults like a Page List structure in Production only?
Regards,
Raghavender
HCA Healthcare
US
@RaghavenderG4330
The issue where your Page Group shows pxResults in Production usually means some rule is mistakenly treating it like a Page List. This can happen if a Data Transform, Activity, or integration (like a REST call) is trying to copy or map a list of values into the Page Group without proper handling. Pega uses pxResults automatically when working with lists, so if a response or logic assumes it’s a list, it may dump everything into pxResults even if the target is a Page Group. Check the rules that populate this property especially in Production and compare them with lower environments to see if there are any mismatches or missing changes. Also, make sure any integration mapping is explicitly assigning data to the correct Page Group structure, not defaulting to a list format. Fixing that mapping or assignment should stop pxResults from appearing