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-173986 · Issue 668934
Updated survey refresh API for switching radio buttons
Resolved in Pega Version 8.6.3
After configuring a picklist with multiple options in a survey framework, it was not possible to select a radio button when toggling between radio buttons on the UI. Investigation showed the values of the radio buttons were not published to Clipboard, causing pyAnswer to be blank. After detaching the webwb_pzsurvey_ui_userscript.js the value was posted correctly and the visible WHEN was working as expected. This has been resolved by updating pzsurvey_ui_userscript to add a timeout on the refresh API call when switching between radio button options.
INC-175533 · Issue 678910
Improved Page compare for page groups
Resolved in Pega Version 8.6.3
Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.
INC-179769 · Issue 671022
Document generation new line formatting made consistent
Resolved in Pega Version 8.6.3
The GenerateWordDocument API and Generate Document shape were not adding new line to a Word document even when Text Area format was used. This was traced to a difference in document generation which varied between adding \n and adding \r\n for new line, causing inconsistent behavior, and has been resolved.