Question
Ernst & Young LLP
Ernst & Young LLP
US
Ernst & Young LLP
Posted: Jan 20, 2022
Last activity: Apr 21, 2022
Last activity: 21 Apr 2022 4:03 EDT
Closed
Pega Client for Windows properties not getting set on refresh with data transform
In Pega Client for Windows whether it is in Offline or Online, I am having issues with the data transform not setting the properties or not refreshing correctly. In the section, I have an autocomplete that is setting the data for 3 other read-only text fields.
I went through various ways to test if there were any issues with the data transform or refresh and these are the results:
- The data transform that is getting referenced in the Action onChange for the autocomplete control is calling a non-parameterized data page. The other steps within this data transform is a simple when condition that is checking to see if a value equals another property and setting 3 properties. Values are not getting set in this scenario.
- I have attempted to have a Run Data Transform action and then a Refresh-Other section on the autocomplete control and the values are still not getting set.
- I have also attempted to refresh the data transform on the Refresh-Other section, but this did not work as well.
- I have also simplified the data transform that is getting called on the refresh action to only set a property, and I do not see the property getting set in the UI.
#1 is the way we want to implement this solution to refresh the data on the UI.
Would anyone have any suggestions of what may resolve this issue in Pega Client for Windows? Any help would be appreciated.
***Edited by Moderator: Pooja Gadige to add capability tags***
To see attachments, please log in.
Posted: 2 years ago
Updated: 2 years ago
Updated: 8 Feb 2022 10:26 EST
PEGA
Pegasystems Inc.
PL
I think there are a few possibilities:
- One possibility is that the section is not properly configured. Please ensure it's working on a desktop browser.
- Second possibility is that you are trying to use an action which is not supported in an offline-enabled application. Please note these limitations apply to all offline-enabled applications independently from if the application is online or offline at a given moment:
- Third possibility is that we are dealing with a platform bug. If that is the case, it's very likely that the issue has been resolved in a later 8.4 patch-set release. Is there any special reason why you are using 8.4.3, instead of the latest patch-set release 8.4.6? Please note that even if a bug is identified as fixed in a later patch-set release, it will require a strong business justification to get it back-ported to an earlier patch-release.
Thanks,