INC-119669 · Issue 562588
Special character handling added to filters for table sourced with parameterized RD
Resolved in Pega Version 8.1.9
Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.
INC-119669 · Issue 562586
Special character handling added to filters for table sourced with parameterized RD
Resolved in Pega Version 8.2.7
Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.
INC-118907 · Issue 561071
ClearHighlight called after test steps complete
Resolved in Pega Version 8.2.7
When using a custom delay as part of a scenario test, an orange highlight square was unexpectedly persisting on the portal. To resolve this, an update has been made to explicitly call "_clearHightlight()" after every test case step execution completes.
SR-D88500 · Issue 562655
Eligibility prompt integer values sorted by incremental size
Resolved in Pega Version 8.2.7
In an Offer rule on the Eligibility tab of the Eligibility Builder, an eligibility row using {integer property} comparator {value} had the list of prompt values sorted alphabetically for integer values rather than incremental size when using Select value -> Existing Values. This has been corrected by revising the logic in addValuesToOutputPage to call Report.sort with different sorting algorithm for numeric values. Logic was also updated to call Report.sort for prompt lists.
SR-D85095 · Issue 546339
Updated COUNT logic for strategies with ssavm set to true
Resolved in Pega Version 8.2.7
An error was seen when attempting to save a strategy after setting ssavm to true, indicating an issue in the “COUNT” method in Group By shape. Since the source field is not used and does not need to be evaluated here, the system has been updated to ignore the source field if the operation is COUNT.
SR-D92688 · Issue 551340
Optional feature to improve pxETReport performance
Resolved in Pega Version 8.2.7
Poor performance was seen when using pxETReport. This was caused by the system loading the recent cases widget by looking up all the ET cases within last 30 days, opening each ET case to check if it is from the same pyFrom email address, and then if yes, opening its related service case. On a complex system, this was potentially a slow process. To improve performance, the "Related cases" feature can now be disabled through an overridable 'when' rule.
SR-D74376 · Issue 552258
Check added for string vs boolean for pzscan JSON
Resolved in Pega Version 8.2.7
When calling the CloudRemoteMaintenance/Work-/pzscan API, the response JSON had boolean values in the form of String which caused the JSON parsing to fail. The system was using ClipboardProperty.toStringValue() while generating outbound JSON from the clipboard page, which did not correctly interpret a boolean value. To resolve this, a check has been added that will assess the value and invoke ClipboardPage.toBoolean() when needed so that the value is converted as per type before generating the JSON.
SR-D72389 · Issue 541946
Handling added for JSON with top level array
Resolved in Pega Version 8.2.7
When using serialize mode in a JSON data transform where the Top element structure was Array and the “For JSON only” relation was selected for relation mode, the result had an incorrect JSON structure. In order to support this configuration, generatePropertyAsJSON has been amended to set isTopLevelPageList to true in instances where automap is off, the top level is an array, and the JSON context is updated within the first step. In addition, generatePageAsJSON has been updated to check this flag when processing mappings in order to ensure these context changes are processed, and updates have been made to generatePropertyAsJSON to ensure that the context is popped when appropriate.
SR-D90400 · Issue 563187
Explicit parent added for descendants in subreport to correct summary
Resolved in Pega Version 8.1.9
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-D77095 · Issue 559842
Improved backwards compatibility for imported WSDL and ParseXML rules
Resolved in Pega Version 8.2.7
After update, a Connect-SOAP integration created using the "Connector and Metadata" wizard in Pega 6 was unable to use newly generated WSDL that contained updated elements due to the wizard not updating the Parse XML rules with the updated properties, and two parse XML rules were created in draft mode when the old WSDL was imported and then followed by the new WSDL. If the "Create SOAP Integration wizard" was used instead, the properties and Parse XML rules were generated as expected but a new class was created due to the system removing special characters such as underscore. For example, the imported Connect-SOAP rules used the "XXX-APC_QUOTESERVICE-" class, but the Create SOAP Integration wizard changed this to "XXX-APCQUOTESERVICE-". Upper and lower case differences were also seen between the old and new XML Stream and Parse XML rule names. As a result, it was not possible to either skip or generate new properties into a higher ruleset version in the Connector and Metadata Accelerator. To resolve this, updates have been made which now properly skip the identical properties when generating on top of the existing run. The system now also handles unqualified schemas as it did in previous versions.