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.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-143845 · Issue 603220

Signature support added for external repositories

Resolved in Pega Version 8.4.4

On Accepting the signature for a repository, saving the case cleared the signature from the control, even though the signature was saved into the data repository. This was a missed use case, and support for signature has been added to external repository use.

INC-150249 · Issue 609023

Handling added for missing data transform in offline mode

Resolved in Pega Version 8.4.4

A "data synchronization failed" error appeared when trying to login to a Mobile App that had offline mode enabled. The login worked when offline mode was not enabled. Investigation showed that when the pyDataTransformWhitelistForOffline application rule contained an entry for a data transform that did not exist, DataTransformPackager.canProcess() was throwing a null pointer error trying to access it. This has been resolved by adding a null check.

INC-155971 · Issue 616031

Handling added for missing data transform in offline mode

Resolved in Pega Version 8.4.4

A "data synchronization failed" error appeared when trying to login to a Mobile App that had offline mode enabled. The login worked when offline mode was not enabled. Investigation showed that when the pyDataTransformWhitelistForOffline application rule contained an entry for a data transform that did not exist, DataTransformPackager.canProcess() was throwing a null pointer error trying to access it. This has been resolved by adding a null check.

INC-151446 · Issue 614446

#resolvedissues note:HTML tags removed for Survey Question tooltips

Resolved in Pega Version 8.4.4

After upgrade from v7.1 to v8.4, question rules with rich text along with styles and answer mode as dropdown were not loading in the survey UI and the error " Exception Occurred in Rule-HTML-Section for question QuestionName" was generated. This was traced to the use of HTML tags in the "pytooltip" property. To resolve this, HTML tags will be removed using a regex and the property will be correctly handled from there.

INC-157217 · Issue 631969

Field Service mobile refresh timing updated

Resolved in Pega Version 8.3.6

A configuration in the Field Service mobile app used to select and map data from a modal section to a wrapper section used "pega.fsm.mobileutil.reloadSection" to refresh the wrapper section and make the data visible after the mapping. If the refresh was performed after the initial login, the refresh was done on only a portion of the screen and resulted in incorrect data being shown to the user. However, continuing to fill in the section and then saving and reopening the task displayed the correct results. The issue was reproducible only on the first attempt after clearing cache/date: subsequent uses refreshed properly. This was traced to the timing of the configured actions, which caused the refreshSection action to be triggered before the runDataTransform action execution was completed. This has been resolved by adding code that will pause the action queue until the runDataTransform action completed.

INC-191970 · Issue 680396

Updates made for reviewing online case in an offline app

Resolved in Pega Version 8.7

After developing a Field Service Mobile app on Pega 8.3, updating and assessing the Mobile App on Pega 8.6 resulted in a flicker in the back arrow for returning to the work list. This was traced to WebViewManager not being available for online cases in offline apps, and has been resolved by adding an update that will use attachOnload/detachOnload if WebViewManager is not available. In addition, an issue with creating a space or document on mobile has been corrected by using the onViewRendered method instead of attachOnload for the offline app case.

INC-150578 · Issue 607479

rich text editor control handling updated for survey display text

Resolved in Pega Version 8.4.4

After upgrade, Display text in the survey was missing for the question rules which used Rich Text Editor control. This has been resolved by updating the system to copy DisplayText and QuestionText into DisplayTextWrapper.

INC-135015 · Issue 591980

Handling added for overriding questions rules

Resolved in Pega Version 8.4.4

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-161214 · Issue 640893

Push notification of shape-created child case opens correct case

Resolved in Pega Version 8.7

In a scenario with two cases, CaseA and its child case, CaseB, when CaseB was created from CaseA with a standard shape and a push notification was sent right after creation, the "Custom message" notification received on a mobile device opened CaseA instead of CaseB. If CaseB was created as a standalone case, the push notification opened it properly. This was traced to an edge case where the Primary.pzInsKey was empty because the child case was not available in database when the push notification payload was created by push shape, leading to the CaseID retrieved by getInstanceHandleFromPage to fetch the parent Case ID instead. This has been resolved by modifying the process to get the pzInsKey from the step page.

INC-183485 · Issue 681360

Updated background refresh for off-screen worklist

Resolved in Pega Version 8.7

After update, performance impacts were seen on the field service mobile app. This was traced to Worklist refresh, and has been resolved by adding an update which will postpone the refresh when the worklist webview is in the background (not visible on the screen).

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