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-C12199 · Issue 360112

Pass pyFailMessage works to include additional error message on mobile

Resolved in Pega Version 8.1

Using a custom authentication activity to set an error message to be displayed on login screen by using:Param.pyFailMessage = "custom error message" Param.pyChallenge = @java("PRAuthentication.DEFAULT_FAIL_STREAM") worked fine on Desktop but on mobile resulted in the generic "The information you entered was not recognized." message that is hardcoded in pyWeb-login-mobile-authentication.js. This was a missed use case for handling scenarios where additional message error data should be sent in response, and has been resolved.

SR-C12279 · Issue 354259

rule-ruleset-version correctly cataloged to hotfix

Resolved in Pega Version 8.1

While importing DL for the PCS application, rule-ruleset-version was not getting cataloged to the hotfix manager. This was traced to the failure of the pre-installation initial scan. As recent system changes now support non-versioned rules by looking at the save time, the Rule-RuleSet-Name and Rule-RuleSet-Version will both be treated as valid for scanning and cataloging to avoid this error.

SR-C12338 · Issue 353057

Corrected code to prevent infinite loop in PegaGadgets

Resolved in Pega Version 8.1

The out-of-the-box Activity : "@baseclass.pzPopulateRecentGadgetList|Pega-Gadgets:07-10-23" contains logic in its Java Step (3) that under certain unusual circumstances caused an infinite loop to occur, locking up the Thread indefinitely. This has been fixed.

SR-C12339 · Issue 386340

ZipFileListOnServer activity modified to only create instances for zip files

Resolved in Pega Version 8.1

When the Hotfix Manager was run on the ServiceExport directory, the Next and Cancel buttons did not render. Analysis showed the system was creating the PRFile instance for all of the files from the directory, and an exception was being thrown when am instance was created for a file that had illegal characters in its name. To correct this, the pzZipFileListOnServer activity has been modified to only create the instances for files which start with "dl-" and end with ".zip".

SR-C12455 · Issue 356026

BIX date property extract to Teradata database fixed

Resolved in Pega Version 8.1

BIX extract was failing when extracting date property to a target Teradata database. To resolve this, DatabaseUtilsCommonImpl.java has bene updated to insert the null value as a varchar instead of Timestamp type.

SR-C12689 · Issue 356526

Improved logic for CorrNew activity email IDs

Resolved in Pega Version 8.1

When there were only two work parties and their email IDs were same, for example using a Bcc address, the formation of email ID string to CorrNew activity included an extraneous quote mark that caused the email to fail. The formation logic has been reworked to resolve this problem.

SR-C12730 · Issue 355808

Data page change detection refactored for improved performance

Resolved in Pega Version 8.1

In order to improve performance, the engine API used to detect changes in a data page has been modified from using a hash comparison via the getJSON sort to using a new lightweight clipboardpagechangeindicator.

SR-C12912 · Issue 357849

Customization added to ReviewSurvey

Resolved in Pega Version 8.1

An enhancement has been added to allow customization of ReviewSurvey by using QuestionPageName as parameter and including the new section PreReviewSurveySection within.

SR-C12957 · Issue 353926

Parse error fixed for pzProgressBar controls

Resolved in Pega Version 8.1

A parse error popup was generated when displaying a section with pzProgressBar controls. This was caused by an error in the Boolean comparison, and has been fixed.

SR-C12957 · Issue 357400

Parse error fixed for pzProgressBar controls

Resolved in Pega Version 8.1

A parse error popup was generated when displaying a section with pzProgressBar controls. This was caused by an error in the Boolean comparison, and has been fixed.

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