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-134618 · Issue 582776

Corrected logic for deep pagelists on mobile

Resolved in Pega Version 8.5.1

After completing a workorder in the mobile app, the synchronization failed intermittently with the error "fail: pyWorkPage - Validation failed: Errors Detected. Finish Assignment action failed as pyWorkPage has messages: Validation failed: Errors Detected. ... The page contains an undefined property: .pxUniqueElementID". This was traced to incorrect logic for handling deep pagelists, and has been resolved.

INC-131961 · Issue 571700

Mobile app correctly determines online status after sleep

Resolved in Pega Version 8.5.1

After not using the mobile device for some hours, the app was not recognizing that the device had become online again and continued to show the red 'offline' bar. Restoring network connectivity required logging off and relogging into the network. This was traced to a bug in Android webview which causes window.navigator.onLine to return as false after wakeup despite the connection being present. To resolve this, version 8.5.103 of PIMC (Pega Infinity Mobile Client) contains new native mechanisms which are exposed to the webview as plugins and that work completely independent of webview.

INC-130727 · Issue 573340

Resolved mobile app java.lang.OutOfMemoryError

Resolved in Pega Version 8.5.1

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-135159 · Issue 580675

Logic updated for deepMergeObj API

Resolved in Pega Version 8.5.1

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-131991 · Issue 583041

Logic updated for deepMergeObj API

Resolved in Pega Version 8.5.1

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-137352 · Issue 583664

Mobile app improvements for poor connectivity conditions

Resolved in Pega Version 8.5.1

When the mobile app was used in areas with poor data network connectivity, the screen was freezing or a number of sync errors were seen. Improvements have been made in the processing and wait conditions to smooth the functions when connectivity is intermittent.

INC-131592 · Issue 583438

Jsoniter parser upgraded

Resolved in Pega Version 8.5.2

After upgrade, the pxTextinput property Prompt List was being converted into decimal upon clicking finish assignment. This was traced to the jsoniter parser, and has been resolved by upgrading the parser in the jsoniter library.

INC-134497 · Issue 578360

Corrected mobile data transform format handling

Resolved in Pega Version 8.5.2

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.

INC-135015 · Issue 591981

Handling added for overriding questions rules

Resolved in Pega Version 8.5.2

After overriding questions rules and then upgrading/validating Question Groups, questions were not shown. It was necessary to manually edit, save, and refresh for the questions to appear, affecting mainly Rule-PegaQ-QuestionGroup rules. This was traced to missing handling for this usecase. The commit was added in Revalidate and Save, which was committing different data because the upgraded data was not copied back to step page being used. Due to this, the commit in BulkValidateSave was overriding the changes done in the pzUpgradeSurveyInstance activity, and the survey upgrade was failing. To support this use, Page-Copy has been added to pzUpgradeSurveyInstance after the pzSaveSurveyInstance call step to copy the updated data to the step page which will later be committed by BulkValidateSave during revalidate and save.

INC-135720 · Issue 594791

Case link shows in Social messages for the old cases

Resolved in Pega Version 8.5.2

After upgrade from v7, the case link was not visible for the cases that were created in the old platform version. In Pega 7.1.7, metadata was stored in .pyPrivacyContextor while the later versions are using .pxContextType for Case type to show the related data. To resolve this, new properties have been implemented to hold the Case ID link

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us