SR-118106 · Issue 174462
Improved accessibility for UI properties
Resolved in Pega Version 7.1.7
When a property is put on the UI from a different Page the generated UI was not setting the correct LabelFor - it striped the Page context but didn't strip the dot from the front of the property. Accessibility JAWS and other assistive technologies were therefore not associating the label with the input and did not read it out for the given input. The label generation function has been changed to address the reported issue.
SR-118111 · Issue 175580
Drop-down focus modified for accessibility
Resolved in Pega Version 7.1.7
When an onChange event is set on a dropdown (select) while using the accessibility framework, the focus automatically shifted onto the next element in the UI. This was not the desired behavior, and the system has been modified.
SR-118159 · Issue 174990
Improved handling for Case notes when spellchecker is active
Resolved in Pega Version 7.1.7
If a lot of content was added for a case Note, clicking on the Notes tab caused the text to display in a big yellow box which could not be dismissed. This was traced to the spell checker not properly handling RTE's hidden textarea field, and the code has been modified to correct this.
SR-118194 · Issue 170594
Declarative refresh now working for IE
Resolved in Pega Version 7.1.7
When using IE, property changes on the clipboard did not trigger a declarative refresh. This was traced to a duplicate refresh section list that was not getting cleared properly with addition of cross thread change tracking, and has been corrected.
SR-118307 · Issue 172330
Integers with embedded spaces now prompt screen edit during validation
Resolved in Pega Version 7.1.7
If an Integer property was populated with a number with spaces ("12345 67890"), it generated the validation error "** PropertyValueInvalid null .pegaToInteger() Invalid number format (was 12345 67890)". A numeric value with embedded spaces will fail during conversion to Integer, but this will now be caught with a screen edit in the same way a non-numeric character would be during screen validation.
SR-118675 · Issue 172991
Corrected duplicated validation errors
Resolved in Pega Version 7.1.7
In some cases, validation error messages were being duplicated in the display. This was traced to code in the dynamic display being executed twice, and has been corrected.
SR-118725 · Issue 174420
Corrected focus for filter window using WAI
Resolved in Pega Version 7.1.7
With WAI enabled for work object - Audit window- History table - Time column, clicking on Filter window did not properly move the focus to the first element i.e., Add/Remove columns link. The getFirstInputElement API has been modified to fix the reported issue.
SR-118884 · Issue 172536
Create Work correctly encodes Japanese characters
Resolved in Pega Version 7.1.7
When Japanese characters are passed as parameter to Create Work action, the newly created work item was registering cryptic characters instead of the expected Japanese characters. This was traced to a deprecated API, and has been corrected.
SR-119130 · Issue 173876
"?" character allowed in URLs with get requests
Resolved in Pega Version 7.1.7
When specifying an Alternate Domain URL for a link, if the URL contained a GET request followed by parameters ("?get&p1"), the URL was modified by SafeURL to include an "=%26" between the "?" and "get" ("?=%26get&p1") (%26 is url encoding for an ampersand & ). In order to ensure alternate URLs are properly processed when they contain "?", a check has been added.
SR-119158 · Issue 175351
Amended login caching to be compatible with new versions of Firefox
Resolved in Pega Version 7.1.7
When using the latest versions of FireFox browser (32+), there was a problem with logging in again after logging out. This was caused by a change in the cache engine for Firefox, and the system has been updated to compensate for the difference in caching.