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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-D91532 · Issue 556404

Resolved Clear Cache error for mobile client

Resolved in Pega Version 8.2.7

When attempting to clear local storage while logged into the Mobile Client, the error message "You need to be able to connect to the server in order to clear the storage" appeared. This was traced to the application being configured to disable a user's web session immediately after log in, and was due to the "Clear Cache" functionality failing while attempting an AJAX request to invoke the server's "pzAmIOnline" activity. While there was a workaround of using the check box "Access group requires a connection for portions of the application", this has been resolved by updating the Settings - Clear Cache functionality in order be able to detect if it's online in a different way.

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-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.

SR-D86079 · Issue 548108

Label truncation added for pinned item title

Resolved in Pega Version 8.3.3

While pinning a Space, document, or URL, the length of the item title was causing validation issues if it exceeded 64 characters. This has been resolved by modifying the pzGetPins activity to truncate pyLabel to 64 characters using the truncateLongText function.

SR-D74246 · Issue 543724

Accessibility improved for Pega Survey Question pages

Resolved in Pega Version 8.3.3

Question Pages in Pega Survey lacked accessibility. This was traced to aria-label not being generated for Radio buttons and Drop-downs, and "title" not being generated for other controls used in Question and Question Pages. This has been resolved.

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.

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