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.
SR-127922 · Issue 196912
Fixed child validation in repeating tree grid
Resolved in Pega Version 7.1.8
The required validation was not firing in a repeating tree grid for a child item but was working for the parent Item. This was a problem with the Clientvalidation parameter not being set when the child nodes were expanded, and the proper parameters are now being sent for client validation.
SR-127923 · Issue 193684
Localization updated in Developer environment to correctly translate labels if dot or @ is enclosed in double quotes
Resolved in Pega Version 7.1.8
In the Developer environment, the translation/localization wizard was not generating the corresponding field values for labels with text ending with '.'. This was an issue where the function "pzGenerateLabelCellContent" that validated the label text would not process the field if it contained text with a dot (.) or an @ symbol. The system has been updated to perform the localization if those special characters are enclosed in double quotes, and this format should be followed to ensure proper handling.