INC-195321 · Issue 684971
Check added for readonly header control
Resolved in Pega Version 8.7.1
After configuring an optimized grid and adding a checkbox control in the header with editable options, when the control in corresponding column was configured as Auto, the checkbox in the header was rendered as read-only. When the control in the corresponding column was configured as "Read-only always" or displayText control was used, the checkbox was rendered as editable control. This was traced to a missing check for pyEditOptions = "Read-only", and has ben resolved.
INC-195581 · Issue 691842
Control menu code minified
Resolved in Pega Version 8.7.1
Minification has been turned on for control menus.
INC-196002 · Issue 684939
Handling added for undefined GadgetOffsetState in Mashup modal windows
Resolved in Pega Version 8.7.1
Following an update, the system was hanging after launching Mashup and submitting from modal window. Investigation showed that in this mashup scenario, when the modal dialog was rendered on click of a button the globally-defined pega.Mashup.GadgetOffsetState object was passed as undefined to the pega.u.d.registerModalListener API due to pega.Mashup getting reset elsewhere in the process. To resolve this, handling has been added for a modal dialog in mashup scenarios when pega.Mashup.GadgetOffsetState is undefined.
INC-197358 · Issue 695308
Resolved finish assignment screen freeze
Resolved in Pega Version 8.7.1
In some assignments of several flows, when the processing was done (finish assignment) the screen only displayed the loading logo. The only way to proceed was by refreshing the browser. The browser console showed the error "Uncaught TypeError: Cannot read properties of null (reading 'undefined') at setTargetValuesSuccess (expression_calculation_1480665478.js!!.js:1) at k". The error did not occur when using Live UI privileges. This has been resolved by updating the expression calculation.
INC-197410 · Issue 690216
Handling added for invalid numeric range
Resolved in Pega Version 8.7.1
When filtering the range in number column with value as “1000000” , the validation message appeared as "1000000 : This results in an invalid numeric range". This has been resolved with an update to use Data-value to get the non-formatted value for decimal.
INC-197481 · Issue 695584
Accessibility improved for blank field errors in non-auto generated controls
Resolved in Pega Version 8.7.1
When using non-auto generated controls, leaving an edit field blank caused an error message informing that the value cannot be blank. An accessibility issue was seen where this error text was not part of the field label or description, preventing it from being announced by screen readers (NVDA or JAWS) when focus is on the field. This has been corrected by adding aria-describedby in non-template textarea.
INC-198133 · Issue 693110
Data-test-id generated for table header
Resolved in Pega Version 8.7.1
After adding a table to the layout and putting labels on the table headers, the data-test-ids were not displayed in the generated DOM. This was traced to an issue where the test ID was not generated for the table headers, and has been resolved by updating GenerateCellContent to add data-test-id in markup.
INC-199496 · Issue 690005
Corrected quotation mark handling for multi select
Resolved in Pega Version 8.7.1
After defining a source for multi select where the selectable list contained double quoted text, for example: Testing for "Double Quotes", the double quotes were converted to single quotes in the selection list. This caused the value Testing for "Double Quotes" to be displayed as Testing for 'Double Quotes'. This has been corrected.
INC-199558 · Issue 693302
Updated calling activities from refresh to use invokeActivity
Resolved in Pega Version 8.7.1
The Refresh DX API was inconsistently throwing an index out of bound exception when using a checkbox which invokeed an activity on check to save and commit the case. This has been addressed by updating calling activities from refresh to use invokeActivity, and a try/catch has been added to capture exceptions and add a page message if the activity is not found or has an error.
INC-199625 · Issue 690720
Handling added for dropdown with duplicate option values
Resolved in Pega Version 8.7.1
When load behavior used "After screen renders" and dropdown options had duplicate values, a console error was observed and the UI became frozen. This has been resolved by adding handling for scenarios where the dropdown has duplicate option values.