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 562585

Special character handling added to filters for table sourced with parameterized Report Definition

Resolved in Pega Version 8.3.4

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-120343 · Issue 573076

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.3.4

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-125641 · Issue 573385

Column Filter working with class join

Resolved in Pega Version 8.3.4

When a class join was configured in the report definition and the report was edited to include new columns from the joined class, a "Filter condition invalid" error appeared in the tracer after adding a filter condition to a new column. This was only observed when the property added was a decimal property, and did not happen for a text property. The filter worked as expected after re-saving the property in the report definition in Designer Studio. This was traced to the data type being passed as "DECIMAL" for decimal fields, which did not match the logic used to set the filter value, and has been resolved.

INC-125752 · Issue 566169

Tab Titles show the correct title on hover of tab name

Resolved in Pega Version 8.3.4

When clicking on the case stages information from the Dashboard Case Manager to open the stage information in a new tab, hovering on the tab name displays the title of the case stage name. If there are two stages, clicking on the first stage opened it in a new tab and the title of the tabname on hover was correct. However, clicking on the second stage name to open the other stage in the same tab did not display the correct title when hovering on the tab name. This has been corrected by updating the code for the JSON configuration object.

INC-127085 · Issue 563456

Arch Chart Min/Max display correctly

Resolved in Pega Version 8.3.4

The minimum and maximum on the 270 degree arch chart were not working as expected. The minimum value for the LABEL changed, but the actual range of the chart did not. For example, if the chart label for the minimum values showed as 50, the actual range for the chart was still 0-150, and the first segment of the chart did not display the correct color. This has been corrected by updating the functions for handling chart limits.

INC-128899 · Issue 578023

Resolved BIX Extract Summary Status Count mismatch

Resolved in Pega Version 8.3.4

A mismatch was seen between the summary of the Extract Summary Status Count in the Execution History stats versus the logs, for example the execution history saying 98.74% completed while the log says 100% or 100.45% completed. Investigation showed there was mismatch in the query based on the filter value given in the extract rule and the where clause in the query that resulted in an error in calculating percentage in case of any exception. This has been resolved.

INC-129880 · Issue 573726

Updated locking for deleting a scheduled report

Resolved in Pega Version 8.3.4

Attempting to delete a report shortcut from the Case Manager portal resulted in the error "Error in Obj-Delete-By-Handle com.pega.pegarules.pub.database.LockGoneException: Save, Delete or Commit has failed because lock "PEGA-SCHEDULEDTASK" is not held". This has been resolved by enabling locking for Obj-Delete-By-Handle in the pzDeleteShortcutPostActivity7 activity.

INC-131942 · Issue 574323

Orphaned CSS reference removed from DisplayReport harness

Resolved in Pega Version 8.3.4

An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.

INC-133827 · Issue 576190

Cluster stabilization and node shutdown enhancements

Resolved in Pega Version 8.3.4

When a node has problems like reaching its primary it can be reinitialized, but the shutdown process at the beginning of the reinitialize phase did not work correctly for primary-eligible nodes because there was an uncaught exception. There was also a problem with the updating of replica count if the request was executed remotely just after node shutdown: because a remote node was chosen from all possible nodes not offline, a node with a cluster communication problem could be chosen and the replica count would not be updated. While these issues are only found on clusters with frequent restarts, they may be seen during upgrades and planned rolling restarts. Enhancements to cluster stabilization and node shutdowns have been added to address this.

INC-136320 · Issue 582725

Ad hoc reports saved successfully in private categories

Resolved in Pega Version 8.3.4

After upgrade, an error was seen when attempting to save an ad hoc report in a private category. Saving in a public category worked as expected. This was traced to the Rule-Shortcut.Validate activity, which attempted to use the Rule-Shortcut's RuleSet to find the Rule-Category. To resolve the saving issue, the Rule-Shortcut.Validate activity has been updated to do an Obj-Open on the Category instead.

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