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-132590 · Issue 590490

Exported Excel from Decision Table wraps correctly

Resolved in Pega Version 8.2.8

After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (

INC-136571 · Issue 597386

Filter by Rule Resolution enabled for GetPegaExpressFieldsByType

Resolved in Pega Version 8.2.8

After creating a Text Input property of type none in a ruleset version [For ex: Myruleset:01-01-01] and then saving this property in a higher ruleset [Myruleset:01-01-02] and changing the type to promptlist, the same property appeared twice in Eligibility Builder [Content -> Offers -> Eligibility Builder]. This has been resolved by enabling the "filter by rule resolution" option in the Rule-Obj-Property.pzGetPegaExpressFieldsByType report definition to make sure rules are fetched from the latest ruleset version only.

INC-140272 · Issue 595252

Report definition performance improvement

Resolved in Pega Version 8.2.8

Performance issues were seen with the pzOperatorsByWorkGroup report definition. This was traced to the report definition is adding an UPPER function for edit filter properties which caused it to take more time to run when combined with an ignore case check in the filters of the Report Definition. This has been corrected.

INC-125803 · Issue 568662

Cross-site scripting updated on activities

Resolved in Pega Version 8.2.8

Additional Cross-site scripting work has been done on activities.

INC-135095 · Issue 581846

Tracer toolbar shows correctly in Microsoft Internet Explorer

Resolved in Pega Version 8.2.8

After upgrade, the developer toolbar for the tracer pop up was not visible in Internet Explorer. Investigation showed that IE was loading the correct elements, but they were not displaying due to recent updates made to prevent Cross-site scripting vulnerabilities for the tracer. This has been resolved.

INC-135349 · Issue 583002

Unit Test Ruleset rules do not count against Guardrails

Resolved in Pega Version 8.2.8

Although the documentation indicates that rules in a Unit Testing ruleset should not count against the guardrail score or unit test coverage, when branching a unit test ruleset, the branch did not carry the same unit test flag value as the source ruleset and the rulesets were counted as a result. This has been resolved with an update to ignore testrulesets in guardrail and pegaunit calculations.

INC-141179 · Issue 591821

Repaired test cases for When rules

Resolved in Pega Version 8.2.8

When running a Pega test case for a When rule, values that were set up before the rule execution on RunRecordPrimaryPage disappeared from this page. This has been resolved by creating the RunRecordPrimaryPage before loading Setup Pages.

SR-A10345 · Issue 221893

Removed unexpected validation from Page-Change-Class

Resolved in Pega Version 7.2.1

Validation errors appeared on the review screen when tracer was enabled if there was non-conforming data in the non-expanded elements. PDN help for the activity method Page-Change-Class specifies that the method does not validate property values, but the generated java ends up calling DictionaryImpl.validate() and validates the step page without expanding it. Any invalid data in the non-expanded properties would be ignored. However, activating the tracer expands the page and as a result Page-Change-Class attempts to validate all the properties in the page, resulting in errors appearing when appropriate. In order to handle this scenario, validation has been removed from Page-Change-Class method in order to bring the results into line with the help documentation, and if validation is needed it must be added explicitly.

SR-A11437 · Issue 225251

Improve page sync and locking to avoid ConcurrentModifiedException

Resolved in Pega Version 7.2.1

There was a possibility that data page could be modified simultaneously and generate a ConcurrentModificationException, for example where a background thread is expanding a page to check messages at the same time a user thread is expanding the page to fire declaratives on read-only data page before marking it read only. This has been resolved by synchronizing access to a data page instance whenever there is an attempt to expand it from boundaries of data pages code.

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