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-116587 · Issue 170222
Clarified default values for Create Class
Resolved in Pega Version 7.1.7
The Create Class screen was offering default values that had the potential to lead to classes being created in an incorrect / invalid part of the Class Structure. This has been corrected.
SR-116606 · Issue 169617
Error display settings improved for modal windows
Resolved in Pega Version 7.1.7
If a flow was run in a modal window, the Field-level error display setting on the harness was not being accurately reflected, i.e. if the field level error display option is set to "Full Text", a validation icon is displayed instead or in addition to the text. This has been corrected.
SR-116608 · Issue 173164
Removed periods after page numbers to improve accessibility
Resolved in Pega Version 7.1.7
In some cases the JAWS screen reading software was reading out page numbers for paginated grids including a trailing period / full stop character, such as "2." reading as "two point". Since the page number will always be a whole number, the period/point character has been removed.
SR-116613 · Issue 170409
JAWS no longer reads out table structures
Resolved in Pega Version 7.1.7
When JAWS encountered tables, it considered them to be data tables if there were no aria labels or roles defined on it and proceeded to read out the table structure to the user. If one of the td had ' ' it read out as blank. Table tags being generated for layouts are now given a "role" attribute as "presentation" for accessibility compliance: this will mark the table structure not to be read out by JAWS. In addition, JAWS will read out any html associated to the input rather than the aria-label format information.
SR-117230 · Issue 172209
JAWS no longer reads out table structures
Resolved in Pega Version 7.1.7
When JAWS encountered tables, it considered them to be data tables if there were no aria labels or roles defined on it and proceeded to read out the table structure to the user. If one of the td had ' ' it read out as blank. Table tags being generated for layouts are now given a "role" attribute as "presentation" for accessibility compliance: this will mark the table structure not to be read out by JAWS. In addition, JAWS will read out any html associated to the input rather than the aria-label format information.
SR-116648 · Issue 170323
Form level messages retained by parameter for Tree layout
Resolved in Pega Version 7.1.7
Error messages were not retained when "Select On Load" option was selected for the Tree control. By request, an enhancement has been added through the parameter pega.u.d.KeepMessages, and the clearing of page messages will be done depending on this parameter, both in client and server.
SR-116661 · Issue 169635
TrackSecurityChanges enhanced to capture index information
Resolved in Pega Version 7.1.7
While the properties of a pagelist are displayed in the TrackSecurityChanges history tab, the corresponding index of what was changed on the page list was not included. In order to more accurately track what is being changed, an enhancement was added with new field values for tracking the index history.