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-D90232 · Issue 555780
Combo charts now support conditional colors
Resolved in Pega Version 8.2.7
An enhancement has been added to facilitate the use of conditional colors in combination charts.
SR-D90750 · Issue 549580
Search behavior change after update corrected
Resolved in Pega Version 8.2.7
After update, changes were seen in the search behavior that included the toggle button at the top left corner of the landing page becoming disabled when re-indexing was in process, the Re-index buttons becoming disabled and a cancel button appearing in place of the re-index button for the specific index category being indexed, indexing done through batch indexers not presenting progress in the document size column every 10 seconds but instead presented the whole row for the index category as blank, and progress being indicated by the changing figures under the Queue Information section on the Search Landing Page. This was due to a conflict in which ruleset was highest after rulesets were imported during update, and has been resolved by updating pzLPSearchManagerReIndexSection to use the correct version of the ruleset.
SR-D91038 · Issue 553164
Corrected report with combo chart in Case Manager portal
Resolved in Pega Version 8.2.7
After adding the required columns a report in the report viewer and then adding a combo chart and dropping the summarized column on the y-axes and group by column on X-axis, clicking on "done editing" generated the error "pyUI.pyChart: You must have at least two Aggregate Columns in the chart series .pyUI.pyChart.pyDataAxis(1).pyChartOutputType: A Combo chart requires at least 1 Chart Type be a Column". Investigation showed that the second DataAxis page was getting deleted in the pzCleanChartDataAxis activity, causing the validation to fail. This has been resolved by adding a 'when' rule to "pzChartIsSingleY" that checks for "SingleYAxisClustered" chart and refers the same in pzCleanChartDataAxis to skip the data axis deletion.
SR-D94002 · Issue 553766
Export to Excel cell style control added
Resolved in Pega Version 8.2.7
If a column was formatted with an auto generated numeric control, a new cell style was generated for every row during the export to Excel process. Since there is a limit on the amount of cell styles, once the number of rows in the file was greater than 64000 an error was generated. To resolve this, the system will disable the creation of a new cell style for every instance when an auto-generated numeric control is used.
INC-185824 · Issue 676630
Corrected filtered column list sorting in Report Browser
Resolved in Pega Version 8.6.5
Sorting was not working in Report Browser for a column list when a filter category was selected. This has been resolved by modifying the pzReportListSort activity to set the correct parameters in step-1 and setting pzSetCategoryParam to retain the sortTitle parameter in step 1 with an added step -2 to call the pzReportListSort activity.
INC-205464 · Issue 721607
Performance improvements for KYC query
Resolved in Pega Version 8.6.5
The GetApplicationKYCTypes report definition was exceeding the default maximum elapsed time of 30 seconds, causing all cases which were part of the due diligence milestone in Client Lifecycle Management framework to be auto-completed. This has been resolved by improving the KYC Items query logic by removing mergeJoin and adding HashJoin Hints.
INC-210837 · Issue 707179
DateTime property correctly formatted in Report Editor
Resolved in Pega Version 8.6.5
When a list report was created via the Report Editor, dragging and dropping a date time property which was embedded inside another page and choosing the format as Date and Time resulted in the property taking pxTextInput instead of pxDateTime. This has been resolved by updating the pzMergeAutoGenForProp activity to get the correct class name for embedded page properties.
INC-211590 · Issue 711018
Auto-complete and calendar popover alignment corrected
Resolved in Pega Version 8.6.5
An issue with the container alignment of the auto-complete and calendar dropdown popovers has been resolved by removing styling in the pyReportEditorStyling .css which was causing the issue.
INC-212157 · Issue 721532
Report filter values correctly displayed
Resolved in Pega Version 8.6.5
The data page name was being displayed in report filters instead of actual values. This was traced to a missing step in the activity pzResolveCopyFilters which was needed to get the data page values in the report filter prompt, and has been resolved.