INC-220989 · Issue 719866
Improved accessibility on create harness
Resolved in Pega Version 8.6.5
Hitting the tab key was navigating out of the popup on the create harness. This has been corrected.
INC-222507 · Issue 721695
Helper text added to clarify maxlength enforcement
Resolved in Pega Version 8.6.5
It is possible to enter more characters into a browser field than is specified by the maximum character limit unless read-only formatting is used. This is due to the resulting HTML input tag having the type of number, which leads to the browser default behavior of not honoring the maxlength attribute. In order to clarify this, helper text has been added with the message "Min and Max characters are ignored for type Number when 'Display value using read-only formatting' is unchecked."
INC-222922 · Issue 722993
Validations fire on collapsed accordion layouts
Resolved in Pega Version 8.6.5
Client validation was not firing on the selected tab of a layout group if the accordion layout was collapsed. If focus was switched to the second tab, the client validation on the first collapsed tab did not work. This has been resolved by modifying the 'else if' condition to pass the validation for the fields places in layout group tabs.
INC-224446 · Issue 724369
Load more works in non-templatized layout
Resolved in Pega Version 8.6.5
After adding a repeating dynamic layout inside a tab group layout (which is a deprecated feature) to make it non-templatized, the progressive pagination option to show the "load more" button did not work. This was caused by the load more functionality having a dependency on pega.ui.RDL even though pega.ui.RDL was not available in case of a non-templatized grid, with the result of generating an exception which broke the flow. This has been resolved by adding a null check which will allow the flow to proceed whether the grid is used inside non-auto-generated or auto-generated elements. Please note that it is strongly recommend to update any deprecated layouts to Layout Group as it is a best practice to keep the code updated to avoid any compatibility issues.
SR-123525 · Issue 186662
Added handling to maintain f ordered list styles in send correspondence
Resolved in Pega Version 7.1.9
In the send correspondence, if the ordered list format was selected and then deselected and again selected, then the bullet points or numbers appeared differently. Handling has been added to maintain the correct appearance through multiple changes.
SR-125651 · Issue 189974
Error icons and localization corrected for repeating tabs headers
Resolved in Pega Version 7.1.9
The error message indication was not appearing on the tab header of repeating tabs. In addition, the tooltip of that icon was not being correctly localized. These issues have been corrected.
SR-127915 · Issue 203511
Resolved NPE for URLEncryption in grids
Resolved in Pega Version 7.1.9
When URLEncryption is enabled in a grid scenario, the property reference was not generated as expected. In this scenario, the AjaxTrackID was not being passed from client to server due to it being a new harness load where normally a new AjaxTrackID would be created at the server end. To resolve this, the pzActionOpenURLInWindow API has been updated.
SR-128119 · Issue 202650
All localization errors displayed as expected
Resolved in Pega Version 7.1.9
When localization wizard generated errors during translations import, it only displayed one in the UI. This was an issue with the errors pagelist not being fully populated with values correctly in pzImportTranslations Activity, and has been resolved.
SR-129722 · Issue 204564
Removed extra white space appearing with Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.9
Using Microsoft Internet Explorer 8, extra white space appeared above the "Next" button in a screen flow when a declare expression was fired. This has been fixed.
SR-130340 · Issue 204442
Corrected date selection highlight for Date-Medium control
Resolved in Pega Version 7.1.9
When Date-Medium control was used in a section and configured with onchange->refresh section, selecting any date other than today's date and opening the calendar pop up again caused the selected date to not be highlighted in the pop-up. To resolve this, datetimecalendar.js has been modified to set the proper date in cases of cal.dateFormat == 3 (Date-Medium and DateTime-Medium control).