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-116556 · Issue 170813
AllLinksForParticularRule changed from Final to Available
Resolved in Pega Version 7.1.7
The list view reporting limit AllLinksForParticularRule has been changed from a Final rule to an Available rule in order to allow an increase in the number of links shown in the Application Profile. The default is 500.
SR-116585 · Issue 167063
Screen flow previous button repaired in obfuscated IAC
Resolved in Pega Version 7.1.7
When using IAC with obfuscation is enabled, the screen flow 'previous' button was not responding. This was caused by the '\' at the end of the URL parameter being accidentally obfuscated as well, and has been fixed.
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-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.
SR-116716 · Issue 167507
Execute RDB runs in batch mode for very large data sets
Resolved in Pega Version 7.1.7
The executeRDB query was not able to handle very large large data sets, resulting in an OOM error after clicking on "Create Prior Authorization". ExecuteRDB (which is a select query) has been modified to run in batched mode, i.e. run the same query with limit on max rows, so as to avoid OOM when copying the whole result set into the memory object (similar to Report Definition paging).