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-131961 · Issue 571701

Mobile app correctly determines online status after sleep

Resolved in Pega Version 8.4.3

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

Logic updated for deepMergeObj API

Resolved in Pega Version 8.4.3

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 580678

Resolved authorization request errors on mobile

Resolved in Pega Version 8.4.3

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-134497 · Issue 578361

Corrected mobile data transform format handling

Resolved in Pega Version 8.4.3

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

Corrected logic for deep pagelists on mobile

Resolved in Pega Version 8.4.3

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

Logic updated for deepMergeObj API

Resolved in Pega Version 8.4.3

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-138954 · Issue 591837

PEGA0042 alerts resolved for unneeded mobile app authorization

Resolved in Pega Version 8.4.3

Many PEGA0042 alerts were seen related to the pegadata.pr_data_admin table and the processing for the pzGetMobileAppConfiguration activity. Analysis showed that some code for generating the OAuth2 client secret is not needed in PRPC 8.2/HC7 7.41.x because authorization_code type is used by default. To resolve these errors, all code responsible for regenerating client secret has been removed from the pzGetMobileAppConfiguration HTML rule.

INC-137709 · Issue 584295

New security role added to restrict access to development-specific classes

Resolved in Pega Version 8.4.3

A new security role and related RAROs have been implemented to allow better security for end users on non-BAC systems. This restricts access to Rules and execution of activities on classes that are development-specific.

INC-139300 · Issue 590270

Additional security for encrypted passwords

Resolved in Pega Version 8.4.3

Handling and cleanup has been updated for encrypted values to enhance security.

INC-130145 · Issue 582854

Null checks added for the presence of roles and dependent roles

Resolved in Pega Version 8.4.3

Frequent Null Pointer errors were being generated relating to SecurityAnalysisForSecurityAdministratorsTask.getCurrentSecurityTaskDetails(). Investigation showed that the Origin and Stack trace tabs were empty, leading to the obj-open of the role failing when the role was not available in the system being utilized. This has been resolved by adding a series of null checks for role existence and dependent roles existence.

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