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-116597 · Issue 169929
Correct report name displaying on chart reports
Resolved in Pega Version 7.1.7
In Case Manager reports, maximizing a report containing a chart showed the URL as the report name if the report title parameter did not have a value. This field has been updated to default to the report's title if the name has not been explicitly set.
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.
SR-116679 · Issue 169078
"Save preferences" button visibility corrected
Resolved in Pega Version 7.1.7
The ability to save report filtering preferences for Summary View was only appearing if the report included an interactive chart. The system has been updated to present the 'Save Preferences' button in all report types.
SR-116681 · Issue 169378
BIX Column length increased
Resolved in Pega Version 7.1.7
At runtime BIX checks the target DB metadata for column length. If it could not find the metadata with schema associated with the BIX DB user, it was setting the length at 32 characters even if a larger column length was specified in PRPC and SQL. This was due to a mismatch in the stored value location, and has been corrected so BIX will reflect the length specified on the Extract rule form.