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-136264 · Issue 582472

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.5.1

In order to present an improved interface for customers interfacing with chatbots, the code has been updated so that the recipient's chat scroll will remain at the top of an answer that would scroll off the screen.

INC-139018 · Issue 587715

Rules updated to handle Outlook change that displayed multiple/duplicate email responses

Resolved in Pega Version 8.5.1

In Pega Email Triage case, all the replies were displayed along with the original email body, meaning for each and every reply, Pega showed the original email body and duplicated the data. This was traced to an update made by Microsoft in the Selector function of Outlook Windows, and has been resolved by updating the rules 'PyExtractLatestReplyFromHTML' and 'pyRichTextEmailHistorySelector' to work with this change.

SR-D85563 · Issue 551684

Dependencies of module.xml documentation update

Resolved in Pega Version 8.5.1

Documentation has been updated to include specifics about adding a dependency in Microsoft JDBC Driver 6.0., under dependencies of module.xml.

SR-D88570 · Issue 550104

Cleanup script topic moved to Post-Upgrade steps in deployment documentation

Resolved in Pega Version 8.5.1

The deployment guides have been updated to indicate that the cleanup script should only be run after the upgrade has been completed, as well as clarifying that this is only required if the clean up scripts have never been run previously.

INC-137009 · Issue 581892

Ad hoc reports saved successfully in private categories

Resolved in Pega Version 8.5.1

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.

INC-136643 · Issue 583367

Orphaned CSS reference removed from DisplayReport harness

Resolved in Pega Version 8.5.1

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-131942 · Issue 574321

Orphaned CSS reference removed from DisplayReport harness

Resolved in Pega Version 8.5.1

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-135719 · Issue 580691

Corrected reference exception for filter on a grid sourced from a parameterized report definition

Resolved in Pega Version 8.5.1

An Invalid Reference Exception was thrown after attempting to apply a filter on a grid sourced from a parameterized report definition. This was traced to work done to allow cross-scripting filters to allow filters to contain special characters, and has been resolved.

INC-137317 · Issue 585402

Security improved for searches

Resolved in Pega Version 8.5.1

Authentication requirements have been added to activities associated with searching.

INC-125641 · Issue 573384

Column Filter working with class join

Resolved in Pega Version 8.5.1

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.

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