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 582469

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.2.8

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

Orphaned CSS reference removed from DisplayReport harness

Resolved in Pega Version 8.2.8

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 580689

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

Resolved in Pega Version 8.2.8

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-140110 · Issue 600399

Large filter values accepted in Report Definition edit

Resolved in Pega Version 8.2.8

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.

INC-143191 · Issue 596470

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.2.8

Due to pzGetScheduledTasks listview having a hardcoded limitation of 500 records to be fetched, not all scheduled tasks were being shown in the scheduled tasks landing page. This has been resolved by modifying the pyCreateSummary activity to use a newly created Report Definition to fetch data instead of list view.

INC-144756 · Issue 602724

Security improved for searches

Resolved in Pega Version 8.2.8

Authentication requirements have been added to activities associated with searching.

INC-120343 · Issue 573075

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.2.8

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.

SR-D90400 · Issue 563185

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.2.8

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-139018 · Issue 587716

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

Resolved in Pega Version 8.6

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.

INC-142930 · Issue 600768

Email history will be stripped from case replies

Resolved in Pega Version 8.6

When sending an email reply to a case, the entire email history (all previous emails in the email chain) was attached to the case as part of the reply.To resolve this, updates have been made so the system will strip history only when it's a follow-up mail. In addition, an issue with duplicate attachments has been corrected, and attachments from trailing mail will not be copied to a new post.

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