Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

INC-119803 · Issue 561684

Placeholder text added for question dropdown sourced by a datapage

Resolved in Pega Version 8.3.4

In a flow action with question pages where each question page was configured with a set of question rules, one question which displayed a country list in a dropdown sourced from a datapage always displayed the first value by default in the dropdown instead of place holder text (like Select..). In addition, the default selection value of the dropdown was not saving to the clipboard on submission of the flow action, causing it to appear in the UI like the first value had been selected even though nothing was saved on the clipboard. These issues have been resolved by adding place holder text in pzSetQuestionStreamSimpleDynamicSelect for a dropdown with a datapage source.

INC-120326 · Issue 564434

Landing page refresh modified to avoid frequent reloads

Resolved in Pega Version 8.3.4

Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.

INC-126114 · Issue 562176

Spaces member count method updated

Resolved in Pega Version 8.3.4

When a space contained more than 50 members, it always displayed the count as 50 even though the Spaces section showed the correct count. This was due to a pagination setting that had a maximum of 50 records set, and has been resolved by using the GroupMemberCount DP instead of AllMembers to retrieve an accurate count.

INC-127347 · Issue 574900

GenerateAttachControl updated for iOS compatibility

Resolved in Pega Version 8.3.4

It was not possible to upload files from an iPad using the Google Chrome browser when the "Attachments" control was used in the application. The attach control flowaction was not opening to select any files, and attempting to directly open the folder to add attachments showed them as grayed out. This was traced to the "Accept" tag not being supported in iOS, and has been resolved by removing accept= / from pzGenerateAttachControl .

INC-127651 · Issue 563337

FS mobile app presents error message when attempting to open a workorder when offline

Resolved in Pega Version 8.3.4

When working online in a mobile field service app, it is possible to open a resolved work order from the worklist. However, when attempting to open a resolved work order while offline, a screen is shown where the option is to logout. To resolve this, the PIMC version has been updated to 8.4.302 which will present the error "Cannot perform this operation when offline".

INC-130727 · Issue 574267

Resolved mobile app java.lang.OutOfMemoryError

Resolved in Pega Version 8.3.4

After working with the mobile app for a period, logging in failed and the app crashed with java.lang.OutOfMemoryError exceptions. This was traced to each sync adding a new version of allow-list datapages to the client store which were not cleared, and has been resolved.

INC-131991 · Issue 583040

Logic updated for deepMergeObj API

Resolved in Pega Version 8.3.4

Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.

INC-133301 · Issue 580680

Resolved authorization request errors on mobile

Resolved in Pega Version 8.3.4

After upgrading and rebuilding the APK with the HC Client Version – 7.41.8-SNAPSHOT, numerous "PYREDIRECTAUTHORIZATIONREQUEST" alerts during mobile interactions caused system performance issues. This was traced to a change in the handling for OAuth2 tokens and related to missing pyClientID column in the database table which forced the system to read all records from the table, and has been resolved.

INC-133749 · Issue 573811

Nested MergeDefinition logic revised

Resolved in Pega Version 8.3.4

When processing a workorder on a mobile app, editing the data of the workorder and related tasks that contained page list properties while offline worked as expected, but when the data was synchronized to the server changes in the page list properties disappeared. This was traced to a logic issue related to merging multiple-level complex nested pagelists, and has been resolved.

INC-134497 · Issue 578362

Corrected mobile data transform format handling

Resolved in Pega Version 8.3.4

An intermittent issue was seen in the mobile app where data was not propagated properly because a Data Transform failed. The error "Failed to run data transform fs_work_task_plannedtask_settaskdetailsfromparent TypeError: sourceProperty.getValue is not a function" was generated. This was traced to a difference in the generated data transform format where a success scenario considered “Problem” as a page, whereas a failure case considered the “Problem” as a property and the getValue() operation failed. This has been resolved.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us