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.
INC-199817 · Issue 690108
Corrected decimal handling in integer control
Resolved in Pega Version 8.7.1
An integer property was accepting decimal values on screen and not throwing default integer validation errors. In addition, the place holders shown on the integer controls on the screen were decimal values. This has been resolved by restricting the decimal values for the integer control with integer property, modifying the code for restricting decimal values for integer field, and updating the code for showing the integer placeholder for integer field.
INC-199953 · Issue 695418
Updated Document-StateTracker reset
Resolved in Pega Version 8.7.1
An unexpected performance issue was seen after refreshing a case. This was traced to the Document-StateTracker taking longer than expected to reset from "busy" to "none", often reaching the 70 second max timeout setting, and has been resolved by calling setNavigationDone so that the document-statetracker dom element updates back to "none" immediately.
INC-201372 · Issue 694014
Accessibility improvements for Cosmos Case Life Cycle
Resolved in Pega Version 8.7.1
Keyboard navigation has been updated to improve accessibility for the case life cycle component. For the "Show stages with expandable steps" configuration, code has been added to hide the steps container when tabbing through the stages. For the "Show stages with steps as overlay" configuration, the "Use form navigation (by tab)" option has been enabled for every repeating dynamic layer inside the steps overlay.
INC-202218 · Issue 692876
Input from Microsoft Windows keyboard numpad enabled
Resolved in Pega Version 8.7.1
After entering a currency amount using the right side number pad keys on a Microsoft Windows keyboard, a mandatory field validation was being thrown on what appeared to be a correct input. This was due to an if condition in the keyup function that caused entries from the right side number keys to not be considered as input, and has been resolved by removing the condition from the pzpega_control_textinput file.
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.