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.

SR-C17653 · Issue 368364

Error logging improved for ParseXML assembler failures

Resolved in Pega Version 8.1

A Rule-Connect-REST call to get user data from an external application during authentication did receive data back from the service, but the ParseXML didn't parse the response and there was no response_GET page or errors logged to indicate the issue. To correct this, the code has been updated to ensure that an error is logged if the ParseXML assembler is unable assemble the rule.

SR-C17679 · Issue 358529

Enhancement to support international currencies in SmartDispute

Resolved in Pega Version 8.1

An enhancement has been added to the Smart Dispute application to support using international currencies. The currency control 'pxCurrencyInternational' is available in the base Pega Platform, similar to the existing control 'pxCurrency' but with format type as 'Text'. The control also has a script that removes any text other than non- numeric, comma, decimal, or negative sign values and supports both comma and dot as decimal separators.

SR-C17971 · Issue 358707

Mobile requestors properly closed at logoff

Resolved in Pega Version 8.1

On mobile, the requestor for synchronization was not released after logoff. Investigation showed that two requestors were started for every mobile login but only one was removed when the session was closed. This has been fixed.

SR-C17998 · Issue 358393

Collapsible headers read one with JAWS / Microsoft Internet Explorer 11

Resolved in Pega Version 8.1

JAWS was reading collapsible headers twice when using Microsoft Internet Explorer 11. A check has been added to resolve this.

SR-C18047 · Issue 362402

Added flag for property messages on a passivated page

Resolved in Pega Version 8.1

A page with messages on a property was submitted twice after passivation has occurred. On investigation it was found that @hasMessages() is returning false after passivation even though a property on the page did have messages. Because the messages were not getting cleared, the application returned the same page to the user, and the page ended up being submitted twice. To correct this, when a page that undergoes passivation has messages, the information that the page has messages will be stored in the encoded page put into the passivation store. During decoding/activation of page, the system will use this flag to determine that page has messages and process them correctly.

SR-C18124 · Issue 362384

Configuration change to avoid Apache Poi zip bomb errors

Resolved in Pega Version 8.1

While importing an Excel sheet to create a workbook instance in Pega on a system that uses Apache Poi, Apache's built-in validations were triggered by what the software interpreted as an attempt to violate system integrity. In this case, a "java.io.IOException: Zip bomb detected!" error was generated when Apache detected a huge amount of data being uploaded to a server; in some scenarios this might be an attempt to eat up all of the server memory and impact server performance significantly, hence the warning. When there are many redundant data values present in an Excel file, the file will be compressed by a very high scale when saving. When the same file is used to retrieve data (during import in Pega) it will expand with the same scale to prepare the actual file. The "Zip bomb detected" exception will occur if the expanded file crosses the default MinInflateRatio set in the Apache jar. Apache includes a setting called MinInflateRatio which is configurable via ZipSecureFile.setMinInflateRatio() ; this will now be set to 0.0 by default to allow large files.

SR-C18180 · Issue 361485

DenyExternal close button localized

Resolved in Pega Version 8.1

Localization has been added for the "Close" button in the final rule DenyExternal.

SR-C18227 · Issue 362399

Customization added to Report Browser

Resolved in Pega Version 8.1

In order to support customization of the Report Browser, the below rules are now marked as available:PZRBSHORTCUTSGRID7 PZRBREPORTACTIONS RULE-HTML-HARNESS CODE-PEGA-LIST DISPLAYREPORT #20151123T213308.460 GMT RULE-HTML-HARNESS CODE-PEGA-LIST PZRRDISPLAYCUSTOMFILTERSECTION #20160512T224721.208 GMT Schedule options and Shortcut/Category options can be hidden via 'when' rules: pyReportBrowser_ShowActions should be set to False to hide the shortcut/category actions, and pyReportBrowser_ShowSubscriptionActionsAndInfo should be set to false to hide the report subscription information. When both rules are set to false, the gear icon on the shortcuts grid and list of Public categories will not be displayed. In addition, the DisplayReport and pzRRDisplayCustomFilterSection harnesses have been made available to allow changing the Microsoft Internet Explorer Document mode.

SR-C18355 · Issue 359131

Fixed dropdown visibility in Results tab

Resolved in Pega Version 8.1

When trying to delegate a decision table with a few result options defined in a "Results" tab, the drop down of options is not available when editing the decision table rule If the checkbox "Allowed to update column layout" is unchecked in the said decision table. This has been fixed.

SR-C18491 · Issue 361186

pyDecimalProperties value honored by Records editor

Resolved in Pega Version 8.1

While downloading a file from the Records editor, the pyDecimalProperties value was not being honored and decimal values were truncated. This 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