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 DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).
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.
INC-175994 · Issue 667481
Removed redundant Microsoft Outlook email interaction chain
Resolved in Pega Version 8.6.2
When opening an email interaction case, the email editor user interface area showed the complete email chain of the email for every new message that came in related to the case. This was traced to the difference in the selectors that various email clients use to construct a response to an email with email history in it, and has been resolved by updating the selectors for Microsoft Outlook in pyRichTextEmailHistorySelector so no conversation is repeated when using that client.
INC-176881 · Issue 669701
Resource added to extract email threading code from message body
Resolved in Pega Version 8.6.2
In some scenarios the case ID was not being sent in the subject of email replies as expected, and the secure tracking code was part of the email body instead. That caused replies back to the email thread to create a new email interaction case instead of properly threading the new message into the conversation. Investigation traced this to some email clients removing space after the tracking code. To resolve this, an update has been made which will extract the tracking code from email-content html if it is found and otherwise fallback to the email body.