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

INC-139130 · Issue 591861

Tab Headers accessible in Report Filter with keyboard

Resolved in Pega Version 8.6

Tab Headers such as "Available Values" were not accessible with a keyboard in the modal to select values for Report Filters. Instead, the focus marker directly shifted to content and toggling between Tabs was not possible. Investigation showed that at runtime for report definitions, the value for prevElement was null, which threw an error and caused the rest of the function to not run. This has been corrected by adding null checks for prevElement and newElement in the function tabClickCallback in the pega_report_events js file.

INC-139295 · Issue 588139

Report Shortcuts resolve datapage parameter references

Resolved in Pega Version 8.6

After upgrade, no results were displayed in case manager portal report browser. This was traced to a data page value that was not resolved at runtime when a data page was used in the report definition shortcut to pass a parameter value. Investigation showed this was due to a change made for v8.4 to correct an issue with data page variables that were not persisting if a report was made with pre-exisiting filters. To resolve this, the logic related to pzResolveCopyFilters has been updated.

INC-140110 · Issue 600397

Large filter values accepted in Report Definition edit

Resolved in Pega Version 8.6

Report definition edit filter values were not accepting large comma separated values properly. This has been resolved by modifying the logic in RRFilters_Logic to use ReportFilter.getReportFilters.

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