SR-116445 · Issue 169717
SOAP settings updated to work with IBM JBK 1.7
Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on WebSphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
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-116719 · Issue 167427
Added handling for SOAP elements with empty case types
Resolved in Pega Version 7.1.7
If customers created a SOAP element with an attribute like Text, the generated WSDL from services wizard did not have a type for the element "CaseStatus" and failed validation with the error "Element 'CaseStatus' with empty content type cannot have text or element content." The XML has been updated to correctly handle this use case.
SR-116761 · Issue 169833
FormatNumber use clarified
Resolved in Pega Version 7.1.7
Attempting to use the "pxFormatNumber" function in an activity step generated the error message "com.pega.pegarules.session.internal.mgmt.Executable cannot be cast to com.pega.pegarules.pub.runtime.StreamBuilderToolKit". Formatter RUF were not intended to be called directly from activities, but RUF has been enhanced to work with reduced functionality in case it is called from activity. The documentation has also been updated to reflect preferred usage.
SR-116778 · Issue 168295
JavaScript error resolved for repeat grids in IE8
Resolved in Pega Version 7.1.7
When using IE8 and Master / Detail editing with a modal window, hitting the enter key to submit a button attached to a repeat grid caused a JavaScript error. This was traced to tabbing forward from the header of a grid: if the grid has no records, the 'no results' message was getting selected as a row and causing a miscalculation. The code has been updated to ensure the 'no results' message is not selected.
SR-116899 · Issue 169326
Edit validation displays literal characters
Resolved in Pega Version 7.1.7
If a property with edit-validate defined on it is included in a section with the control TextArea used, an error message is shown on top of the property if the edit validate returns false. However, the error was not shown as literal but rather displayed the encoded characters and was difficult to understand. This was traced to double encoding of characters like ">" in the displayed string, and has been changed so the literal character will appear.