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.
SR-127470 · Issue 192220
Autogenerated CSS for harness skin fixed
Resolved in Pega Version 7.1.8
When using the autogenerated CSS of a skin in a harness, the tags generated for input types were not applied. This was due to the CSS being incorrectly formed, which has been corrected
SR-127491 · Issue 193606
Resolved runtime error when editing complex grid cells
Resolved in Pega Version 7.1.8
When using grid edit mode inline on a grid with a section inside a cell that includes a checkbox and a 'when' condition, a runtime error appeared when the cell was clicked. This was an issue with the wrong reloadElement being passed in the editRow() API, and this has been corrected.
SR-127513 · Issue 196780
JS error resolved for date control in custom filtering section
Resolved in Pega Version 7.1.8
The Date Picker icon on a custom filter section was not opening the calendar popup unless the clear filter button was clicked. This issue occurred when a summarized report included a chart and had the 'Hide summary data' display option enabled, and was caused by an error in the HTML div function for the popover that used the same name for multiple embedded forms. This has been resolved.
SR-127684 · Issue 194461
Fixed Microsoft Internet Explorer 9 freeze with grid row numbering
Resolved in Pega Version 7.1.8
Attempting to Wrap Up an interaction after viewing a section using a repeat grid with row numbering ON using Microsoft Internet Explorer 9 was causing a browser freeze. This was traced to an API issue where the incorrect frame handling was called for the grid, and has been updated.
SR-127710 · Issue 193207
Code updated for multiple select inside a grid using Microsoft Internet Explorer 9
Resolved in Pega Version 7.1.8
Multiple select inside a grid was not allowing the section to be saved when using the Microsoft Internet Explorer 9 browser. This was due to a JavaScript incompatibility with Microsoft Internet Explorer 9, and the code has been updated.
SR-127811 · Issue 193487
Localization added to RTE tooltips
Resolved in Pega Version 7.1.8
Localization has been added for RTE tool tips.
SR-127884 · Issue 195662
Conditional visibility updated for two-column dynamic layout
Resolved in Pega Version 7.1.8
When using a Two-Column Layout inside a section where each column has a Dynamic Layout with a single label in it, the left column was also hidden if the right column had visibility set to Never. To correct this, CSS selectors have been added to maintain the visibility of the left sidebar column when the main column is empty or missing and the left column is not marked as hidden.
SR-127915 · Issue 198737
Added handling for client-side encrypted data being passed to server encryption
Resolved in Pega Version 7.1.8
A Rule Not Found exception was being generated when using urlencryption and SubmitObfuscatedURL. This was an issue where the system was not prepared to handle URL encryption encoding/decoding that had already been performed on the client side instead of the server side. The Control Generation Logic of pzActionOpenURLInWindow has been updated to handle this scenario.