SR-118077 · Issue 170104
Excessive logging addressed in Pega Mobile 4.3
Resolved in Pega Version 7.1.7
In PegaMobile, the oLog debugging statements were generating excessive log files. This has been addressed in Pega Mobile 4.3.
SR-118081 · Issue 169902
Focus correctly set for dynamic select using accessibility
Resolved in Pega Version 7.1.7
When using a cascading dynamic select control configuration with the PegaWAI accessibility ruleset, setting the focus of the first DS list did not work when attempting to navigate the UI components via the keyboard. When reaching the first DS control, users could only select the next item in the list and then the focus switched to the second DS list immediately. The DynamicSelect control was missing a name attribute, and has been updated to address the focus issue.
SR-118106 · Issue 174462
Improved accessibility for UI properties
Resolved in Pega Version 7.1.7
When a property is put on the UI from a different Page the generated UI was not setting the correct LabelFor - it striped the Page context but didn't strip the dot from the front of the property. Accessibility JAWS and other assistive technologies were therefore not associating the label with the input and did not read it out for the given input. The label generation function has been changed to address the reported issue.
SR-118111 · Issue 175580
Drop-down focus modified for accessibility
Resolved in Pega Version 7.1.7
When an onChange event is set on a dropdown (select) while using the accessibility framework, the focus automatically shifted onto the next element in the UI. This was not the desired behavior, and the system has been modified.
SR-118125 · Issue 171188
Circumstance property value carried into dropdown options
Resolved in Pega Version 7.1.7
If a property of mode single value and type text was created with a defined local list of property values for the property, the value field was not automatically included in the dropdown options when attempting to use this property for circumstance/specialized flows. This was caused by an incorrect refresh section strategy used to determine when to reload the section for the circumstance by property, and has been corrected.
SR-118144 · Issue 171689
Corrected date display in graphs
Resolved in Pega Version 7.1.7
The incorrect date was being displayed in graphs after using the Month function alias to get the first day of the month. The grid displayed when running the show data option in the graph contained the correct date. This was caused by a problematic time conversion in graphs for a specific time zone, and has been fixed.
SR-118159 · Issue 174990
Improved handling for Case notes when spellchecker is active
Resolved in Pega Version 7.1.7
If a lot of content was added for a case Note, clicking on the Notes tab caused the text to display in a big yellow box which could not be dismissed. This was traced to the spell checker not properly handling RTE's hidden textarea field, and the code has been modified to correct this.
SR-118170 · Issue 171859
Property History TaskName field expanded
Resolved in Pega Version 7.1.7
Previously, the TaskName field was limited to 32 characters. This has been expanded to 128 characters.
SR-118174 · Issue 173341
Sorted Report Definition drill downs corrected
Resolved in Pega Version 7.1.7
For some configurations, the Report Definition drill down did not work when it has been sorted. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was caused by an error in calling the page sort in cases where 'do not display group headers' was checked, and has been corrected.
SR-118190 · Issue 172520
Drag and drop work reassignment corrected
Resolved in Pega Version 7.1.7
An error was found that prevented the ability to drag and drop a request from workbasket to worklist or from worklist to workbasket in the Case Manager portal. This has been corrected.