SR-116209 · Issue 166698
Backslash '\' now showing as expected in autocomplete and search
Resolved in Pega Version 7.1.7
The AutoComplete control was filtering out backslash '\' characters when displaying the values in the list of matches, causing failures with search and autocomplete. The Rule-Utility-Function for the getProperty has been corrected to allow '\' to be handled properly.
SR-116220 · Issue 168848
Report drill downs for embedded summary charts open in a new window
Resolved in Pega Version 7.1.7
If a Summary View chart has a drill down to another summary view and then to a list view, when the section is launched, clicking on the pie of a summary chart in the portal gets drilled down to the next level. However, when the chart was maximized (opened in a pop up), it was not drilling down. This was traced to the way actions were configured: when reports were maximized, the main window was set to the parent window and drilling down refreshed the main window and not the maximized window. To remedy this, report drill downs now open in a new window instead of modifying the parent window.
SR-116272 · Issue 168880
Java error resolved for Smartinfo in list view
Resolved in Pega Version 7.1.7
A JavaScript error was being generated in IE8 after viewing the Smartinfo popup with a list view. This was caused by calling the focus API on top of an invisible element, and has been fixed.
SR-116300 · Issue 167205
Added display expansion capabilities for accessibility mode
Resolved in Pega Version 7.1.7
Previously, expanding displays with "+" in the listview category headers required a mouse click. An enhancement has been added to additionally allow use of the enter key at this location to expand and display the attachments of that category type (Notes, Files, Emails, etc.).
SR-116300 · Issue 169067
Added display expansion capabilities for accessibility mode
Resolved in Pega Version 7.1.7
Previously, expanding displays with "+" in the listview category headers required a mouse click. An enhancement has been added to additionally allow use of the enter key at this location to expand and display the attachments of that category type (Notes, Files, Emails, etc.).
SR-116359 · Issue 169895
Dynamic select modified to use display value instead of property value
Resolved in Pega Version 7.1.7
If two different properties were used for display and values in Dynamic select, the value property was shown instead of the display value. This has been corrected.
SR-116359 · Issue 174215
Dynamic select modified to use display value instead of property value
Resolved in Pega Version 7.1.7
If two different properties were used for display and values in Dynamic select, the value property was shown instead of the display value. This has been corrected.
SR-116379 · Issue 167270
Autocomplete enhanced for JAWS Accessibility Mode
Resolved in Pega Version 7.1.7
When using "Auto-Complete" functionality with the accessibility framework, the "Label For" field was not being read aloud by JAWS. For example if the property's label was defined as "Station Code" , the user only heard "Auto complete edit" instead of "Station Code Auto Complete Edit", causing the user confusion as to where they are on the screen. This issue was traced to the labels for the attribute and ID of the input element not being the same, meaning JAWS was not able to find the label for the autocomplete field. To fix this, the function setAriaLabelForAC has been created in pega_ui_doc to collect all of the autocomplete inputs and choose the attribute by figuring out corresponding label. This will work only if the label is in the previous or next cell to autocomplete, and accessibility mode is enabled.
SR-116409 · Issue 170363
Fixed display of harness validation errors
Resolved in Pega Version 7.1.7
When using TabbedScreenFlow with a section containing a repeating grid with enough data to need a scrollbar, checking the "Keep fixed header/footer visible" option and refreshing the section causes the display to shift and render the section buttons behind the harness buttons. This was caused by a misaligned display of validation errors, and has been fixed.
SR-116479 · Issue 170952
Elapsed Time reporting corrected
Resolved in Pega Version 7.1.7
Two out-of-the-box reports, Elapsed Status Time Trend and Average Elapsed Time Per Status, were causing the browser to freeze and stop responding if there were more than 1000 records. This was caused by an invalid value for the datetime units on the category for the chart causing looping behavior. This has been corrected.