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).