SR-127130 · Issue 192558
Localization added for filter values accessed from a new locale
Resolved in Pega Version 7.1.8
After building a Report Definition that used a custom section to display filter values, localization for the filter values was not working if a user logged in with a different locale. Code has been added to handle localizing filter value and label in this situation.
SR-127156 · Issue 191611
Corrected lost lock workflow error
Resolved in Pega Version 7.1.8
In a scenario where "Launch -> Local action" is used on a button without a grid component in the page, opening a modal window with Ok and Cancel buttons in it and then clicking the cancel and Next button on the main screen caused a Lock Lost error. This has been fixed.
SR-127156 · Issue 193608
Corrected lost lock workflow error
Resolved in Pega Version 7.1.8
In a scenario where "Launch -> Local action" is used on a button without a grid component in the page, opening a modal window with Ok and Cancel buttons in it and then clicking the cancel and Next button on the main screen caused a Lock Lost error. This has been fixed.
SR-127156 · Issue 194906
Corrected lost lock workflow error
Resolved in Pega Version 7.1.8
In a scenario where "Launch -> Local action" is used on a button without a grid component in the page, opening a modal window with Ok and Cancel buttons in it and then clicking the cancel and Next button on the main screen caused a Lock Lost error. This has been fixed.
SR-126907 · Issue 193779
Work objects in dynamic container corrected for the AES Manager portal.
Resolved in Pega Version 7.1.8
If a dynamic container is embedded in a section, the work objects opened through AES portal are opened in a dynamic container. When using the AES Manager portal with the Microsoft Internet Explorer 11 browser, work objects would open but then immediately the UI would scroll closed. This was a browser issue where harness tabs with IFRAME in production were not triggering the re-flow for DC tabs as they were for static tabs, and the system has been updated to perform this action correctly.
SR-127161 · Issue 199350
Localization fixed for buttons with shortcut key options
Resolved in Pega Version 7.1.8
Localization was missing for labels on buttons with shortcut key options. This has been fixed.
SR-127231 · Issue 192212
Validation resolved for Class as property reference in Activity Name
Resolved in Pega Version 7.1.8
If the Class was given as the property reference, attempting to enter the Activity Name generated the validation error "Attempting to access the rule in Bad class name: .HARNESSCLASSNAME" and the rule could not be saved. This was traced to the Property reference not being supported for Activity Name, and that has been added.
SR-127306 · Issue 193879
Added special character handling for Tooltips labels and icons
Resolved in Pega Version 7.1.8
Tooltips on labels and error icon were displaying the corresponding escape characters instead of the special characters intended. HTML screens did display these characters correctly. There was a workaround overriding the function in UserWorkForm, but this has been resolved by ensuring the value is html encoded and tooltip is using this value.
SR-127372 · Issue 194363
Fixed ColorPicker control event firing
Resolved in Pega Version 7.1.8
ColorPicker controls associated with a Property which has a default value and configured with an OnChange refresh were not updating when a new color was chosen and instead required an explicit refresh. This was found to be two problems: If there is a value for the property, the background color was set on the inner div and not being replaced when update occurred. Since the color was also being set in the outer div, the inner div setting was unnecessary and has been removed. For the update itself, the processDialog API was not firing the change event upon submit of the modal dialog, but if the event was fired then it implicitly had a refresh added in the markup and was refreshing the section twice. To correct this, the change event is fired from the processDialog API instead.
SR-127388 · Issue 193584
Corrected handling of radio buttons in repeat grids with page groups
Resolved in Pega Version 7.1.8
In the generate radio group, when the radiobuttons control was placed in a repeat grid bounded with page group, the ID attribute of the radio input tag was not in the group and was being generating uniquely, causing the buttons to not hold their value when one was updated. To correct this, the regular expression pattern in pzgenerateradiogroup has been modified to include the page group as well as the page list.