SR-115931 · Issue 169804
Fixed read-only cascading dynamic select in Google Chrome
Resolved in Pega Version 7.1.7
The cascading dynamic select was not working in Google Chrome with ReadOnly Mode. This was traced to an error in the dynamicselect.js, and has been corrected.
SR-115985 · Issue 169316
System updated to handle partially encrypted URLs
Resolved in Pega Version 7.1.7
With URL encryption enabled, certain work types could not be loaded due to an inability to process the partially encrypted URLs. The JavaScript has been updated to correctly handle these URLs.
SR-116025 · Issue 174180
Corrected ability to add rows to a Row Repeat Grid Layout
Resolved in Pega Version 7.1.7
Previously, an error was generated when attempting to add more than 51 rows to a Row Repeat Grid Layout with two more layouts containing other fields. This was caused by a duplicate call to invoke the list section, and has been fixed.
SR-116042 · Issue 170124
Updated newline character for HTML
Resolved in Pega Version 7.1.7
On click-submit, some text paragraphs were being displayed without breaks between them. This was caused by a missing HTML tag and has been corrected.
SR-116209 · Issue 166698
Backslash '\' now showing as expected in autocomplete and search
Resolved in Pega Version 7.1.7
The AutoComplete control was filtering out backslash '\' characters when displaying the values in the list of matches, causing failures with search and autocomplete. The Rule-Utility-Function for the getProperty has been corrected to allow '\' to be handled properly.
SR-116272 · Issue 168880
Java error resolved for Smartinfo in list view
Resolved in Pega Version 7.1.7
A JavaScript error was being generated in IE8 after viewing the Smartinfo popup with a list view. This was caused by calling the focus API on top of an invisible element, and has been fixed.
SR-116359 · Issue 169895
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-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.