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-119669 · Issue 562588

Special character handling added to filters for table sourced with parameterized RD

Resolved in Pega Version 8.1.9

Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.

INC-145810 · Issue 599463

BIX log shows correct corrupted BLOB pzInskey

Resolved in Pega Version 8.1.9

An update has ben made to ensure the correct inskey is shown in the BIX logs for a corrupted BLOB.

SR-D90400 · Issue 563187

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.1.9

When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.

INC-151185 · Issue 618729

OptimizeForLargeResults flag set in BasicListSpecification to avoid OOM

Resolved in Pega Version 8.4.5

As soon as dedicated indexing started for a data type, the JVM heap occupation went beyond 99 and eventually caused a system crash due to an out of memory error. This was traced to the use of the BasicListSpecification API for retrieving results from the database always having the autocommit mode on, which loaded all instances for indexing into memory and interfered with PostgreSQL's cursors (query encapsulation). This has been resolved by adding an OptimizeForLargeResults flag that will be set to on in the BasicListSpecification activity before fetching the keys from the database.

INC-151293 · Issue 630345

Out of memory condition resolved for BIX extraction

Resolved in Pega Version 8.4.5

A node was going down automatically during execution of a BIX Extract rule when working with old objects. Investigation showed this was related to an out of memory error: the work object had nested page lists, and when one of the page lists contained a propertylist which contained more records, the system was trying to add entries to the LinkedList if any properties were missing the reference during extraction. Because LinkedList allowed duplicates, it filled with enough errors to cause the out of memory condition. To resolve this, LinkedList has been replaced with LinkedHasSet, which does not allow duplicates.

INC-152108 · Issue 622371

Logic updated for exporting customized multi-column report definition

Resolved in Pega Version 8.4.5

While attempting to perform an export to Excel for the results of a report definition which had two custom functions for two columns, the error "PRRuntimeException: Section 'pzRDExportWrapper' execution error on page '' of class 'Rule-Obj-Report-Definition'. : The Reference .pyTextValue(2) is not valid. " was logged. The export worked if either one of the columns was removed or if "Display values across columns" in the column settings was unchecked. This has been resolved by updating the logic in PivotTableDataGridGenerator for rowheaders to handle using DisplayValuesacrossColumns with FunctionAliases when not checked on in sequence.

INC-157974 · Issue 621963

Summary Report collapsible sections made accessible

Resolved in Pega Version 8.4.5

In order to improve accessibility, the rules 'RRDataSummaryGeneration' and 'pzDisplayGroupNodeVertical' have been updated so the clickable expand icons in summary reports will append the value of the current group when setting the text "Click to expand or collapse". This will allow JAWS to uniquely identify exactly what will be expanded or collapsed.

INC-158473 · Issue 626275

BLOB decryption API updated for greater flexibility

Resolved in Pega Version 8.4.5

A BIX extraction issue occurred after the class had enabled BLOB Encryption. The errors indicated the BLOB had been persisted in an incorrect stage, causing the extraction of the single item to never complete even though some CSV file was created. This was traced to the API used to read the encrypted BLOB, DatabaseUtilsCommonImpl.getStreamBytes, which had the limitation of decrypting only when a Site-specific cipher existed. To resolve this, the system has been modified to use a different API which works for all encryption modes, PageDatabaseMapperImpl.getStreamBytes().

INC-158874 · Issue 625383

Zero value parameter handling added to Trend Reporting

Resolved in Pega Version 8.4.5

After converting the Summary Views to a Report Definition, the Chart reporting functionality was not working in the Report Definition drill-down reports; whole records present were being fetched instead of only the graph chart count. Investigation showed that one of the parameters in the FilterBy was missing, and that pxSLAAgeTimeliness used 0 instead of null, causing the system to consider all records. This has been resolved by using the "reporting/useNullForUnqualifiedRecords" DSS setting to handle the 0 value and ensure all parameters are present.

INC-159399 · Issue 626766

Report styles color contrast enhanced for accessibility

Resolved in Pega Version 8.4.5

In order to improve accessibility, pzReportBrowserStyles has been updated to change the report creation info color to #00000 to enhance the contrast.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us