INC-205566 · Issue 697057
Ensured correct context for multi-select
Resolved in Pega Version 8.7.1
When using multi-select controls, there was an intermittent issue with selecting values using a mouse click. Using the tab key worked as expected. This was traced to the focus being event triggered multiple times so pega.ctx.dom returned undefined values in the second call.This has been resolved by focusing the target element before creation of capsule to ensure the context remains the same.
INC-206577 · Issue 704422
ParentKey handling updated for for CS portal
Resolved in Pega Version 8.7.1
After creating an interaction in the CPM portal and refreshing the CPMPerformIncludes section (top-level section in the Perform harness) on button click, the focus was set to the first property and a large number of "Uncaught harness context does not exist" error appeared on the console and the screen became frozen. Analysis showed that after the refresh the parentKey property was empty, causing the flow to be executed in the wrong context. This has been resolved by adding a condition to set the parentKey for CS portal 'Add document' scenarios.
INC-206706 · Issue 699986
Placeholder value display made customizable
Resolved in Pega Version 8.7.1
The default place holder value (123,456.78) was displayed for the integer controls even when the placeholder was set to None. This has been resolved by modifying the code to allow customization of the place holder value display. If the "Display value using read-only formatting" option present under editable format is selected and the desire is to show default placeholder for numeric fields, "showDefaultPlaceholderForNumber" with owning ruleset as "Pega-UIEngine" must be created and set to true. If "Display value using read-only formatting" is selected and the default placeholder should not be shown in numeric fields, the DSS should be set to false.
INC-207631 · Issue 701551
Decision Table property chooser made accessible
Resolved in Pega Version 8.7.1
The content of the pop-up "Decision Table property chooser" was not accessible by keyboard navigation. This has been resolved by adding the necessary code for focus inside the iframe.
INC-207632 · Issue 703994
DirtyCheck handling updated for Perform harness
Resolved in Pega Version 8.7.1
In some view scenarios, DirtyCheck was displayed but the "OK/Discard/Save" button unexpectedly closed the case view and returned back to the home page. Investigation showed the DirtyCheck harness was not returning to the appropriate page after the modal screen disappeared, and this has been resolved by changing the "Discard/Save" buttons to an "Ok" button for scenarios where a case is opened in a Perform harness.
INC-208908 · Issue 702171
Placeholder value display made customizable
Resolved in Pega Version 8.7.1
The default place holder value (123,456.78) was displayed for the integer controls even when the placeholder was set to None. This has been resolved by modifying the code to allow customization of the place holder value display. If the "Display value using read-only formatting" option present under editable format is selected and the desire is to show default placeholder for numeric fields, "showDefaultPlaceholderForNumber" with owning ruleset as "Pega-UIEngine" must be created and set to true. If "Display value using read-only formatting" is selected and the default placeholder should not be shown in numeric fields, the DSS should be set to false.
INC-163791 · Issue 704029
Simplified default reference time calculations
Resolved in Pega Version 8.7.1
After a job scheduler was configured to run at Start time = 21:00:00 for Time zone = Europe/London, the scheduler determined 20:00:00 as the next start time. This was due to the calculation for the next start time using the time zone offset calculation pattern for the date and time stored in System-Runtime-Context.pxCreateDateTime, which had difficulty with changes to the time zone definition implemented in the time between the given date and today (meaning the current time) such as daylight savings time. To resolve this, the default reference time from System Runtime Context will be 'now' instead of Date(0).
SR-D69098 · Issue 534042
Export to Excel works for for report definition with duplicate columns
Resolved in Pega Version 8.5
After adding a date column to a report definition (2nd column in the report), the data displayed correctly in the UI but Export to Excel failed with the error "Section 'pzRDExportWrapper' execution error on page '' of class 'Rule-Obj-Report-Definition'. : The Reference .pyDateValue(2) is not valid." This was traced to an out of bounds exception thrown if there were two or more columns with the same calculation. When preparing for export, the column with the duplicate calculation would not get added to the map of report UI fields. To resolve this, the system has been updated to allow report definition columns with the same calculation to be properly mapped to a UI field.
SR-D69108 · Issue 543846
Handling added for drag-and-drop with deleted report templates
Resolved in Pega Version 8.5
After adding a new report, an error appeared when trying to use drag-and-drop to add a column (Page List) from the Data Explorer in the report browser. This was traced to refactor work done to use the Record API throughout reporting: the ruleset on new reports was not being reset from a Pega- ruleset to an application ruleset, causing columns the referenced properties defined outside the platform to be rejected. This use case was missed because case types define their own report templates on creation, but in this scenario those had been deleted. To resolve this, the system has been updated to call pxChooseBestRuleset from pxShowReport in order to enable the use of properties defined in the application prior to saving the report.
SR-D91038 · Issue 553165
Corrected report with combo chart in Case Manager portal
Resolved in Pega Version 8.5
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.