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-127102 · Issue 602697

Synchronized BatchStatus email available for multi-node

Resolved in Pega Version 8.6

An enhancement has been added which will handle synchronization between BatchStatus used in different events on different nodes and send email notifications.

INC-128880 · Issue 592816

Handling added for angle brackets in legacy Chart control

Resolved in Pega Version 8.6

When using Investigative Case Management, some report charts were not rendering correctly. This has been resolved by updating appendFormattedString in AbstractJsonDataGenerator.java to escape angled brackets (< and >) before appending the input.

INC-132169 · Issue 584760

NativeSQL will use inline rule resolution for core components

Resolved in Pega Version 8.6

After upgrade, nodes were going down with a heartbeat error. This was traced to issues with NativeSQL taking a very long time to generate queries due to the overhead in calling multiple complex functions to resolve rules. To correct this, updates have been made to resolve the standard set of functions used by core components inline in NativeSQL function resolution.

INC-133482 · Issue 605003

Corrected isExternal flag not resetting

Resolved in Pega Version 8.6

Corrected isExternal flag not resettingIf an extraction referred to external tables, an isExternal flag that was set to true during the Extraction process did not get reset to false for the tables which were not referring to external. This has been corrected.

INC-137317 · Issue 585403

Security improved for searches

Resolved in Pega Version 8.6

Authentication requirements have been added to activities associated with searching.

INC-138168 · Issue 598100

BIX log shows correct corrupted BLOB pzInskey

Resolved in Pega Version 8.6

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

INC-138931 · Issue 588247

Report Definition filter corrected for integer

Resolved in Pega Version 8.6

When using a report definition where an integer column was added in a filter, clicking on select values did not display the available values as expected. Entering a value and clicking on search also showed no items. Investigation showed the operation was defined as 'Contains' on integer and decimal properties, which was incorrect, and changes have been made in the pzGetselectvalues activity to change the filter operation to 'Equal to' in case of integer and decimal properties.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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