SR-129171 · Issue 195047
Corrected error in order of operations for Numeral builder
Resolved in Pega Version 7.1.8
The Add function in reporting was not returning the proper result when included in an equation with multiple order of operations. This was an error in the Numeral function builder, and has been corrected.
SR-129230 · Issue 196382
Text input handling updated for Microsoft Internet Explorer10/Microsoft Internet Explorer 11
Resolved in Pega Version 7.1.8
When the control for a text box is set to "Integer" and Type is set to "Number" in the Presentation tab while using the Microsoft Internet Explorer10 orMicrosoft Internet Explorer 11 browser, the text was grayed out while typing and any entered text disappeared on blur. This was an issue where If the input type was a number and a placeholder was given, the placeholder was not behaving properly. However, without the placeholder any non-numeric character entered would disappear. To resolve this, the JavaScript for the text input has been updated to render properly for these browsers.
SR-129232 · Issue 197812
LiveUI inspector enhanced to uncover elements inside non-Live UI frames
Resolved in Pega Version 7.1.8
Issues were found with inspecting elements inside non-auto sections from Live UI; Live UI inspector did not point to the relevant UI component, but rather pointed to the header level, causing frames inside an iframe without Live UI Code to be ignored even if they did have elements that could be inspected by Live UI. In order to ensure all elements are caught, code changes have been inserted to loop over all child frames and recall itself with the next frame to cover all elements that can be inspected by Live UI.
SR-129276 · Issue 194879
Replaced missing help search button
Resolved in Pega Version 7.1.8
When launching the Pega help contextually, the button to get to the search field in the Pega help was missing. This has been replaced.
SR-129423 · Issue 198808
Updated responsiveness for certain dynamic column widths
Resolved in Pega Version 7.1.8
At run time, the width of a dynamic layout in a section was not changed as per the transformation and responsiveness was not working as expected for specific column widths. This was an issue with Skin CSS generation for dynamic layouts in generating column widths when another format was applied at a breakpoint, and has been resolved.
SR-129461 · Issue 196393
Security enhanced for RunActionWrapper
Resolved in Pega Version 7.1.8
A potential XSS vulnerability was detected and resolved in the RunActionWrapper.
SR-129465 · Issue 196346
Corrected parameter clearing in MultiSelect control
Resolved in Pega Version 7.1.8
After selecting any value through multiple select and saving it, the saved data was not present when the case was reopened. In Multiselect control, previous values were also being added. This was an issue where parameter values were not being correctly cleared after being used in the MultiSelectList control, and has been fixed.
SR-129525 · Issue 198580
Button question display style now defaults to inline
Resolved in Pega Version 7.1.8
If a question that is marked as required is very long, the asterisk mark was distorted on the radio button label and came up at the extreme end of the label as a separate entity rather than at the end of the label. This was due to the display style for icon required class being set to inline-block instead of simply inline. As the inline display is more appropriate for this field, the default style has been changed to this.
SR-129537 · Issue 195268
Corrected button highlighting for error in selecting required values
Resolved in Pega Version 7.1.8
The Required field label should be highlighted in cases where the value is not selected for the required fields, but the first option of the radio button was being highlighted instead. This was due to misplaced CSS, and has been updated to use the proper label for value to highlight field label in case of error.
SR-129592 · Issue 196979
Scheduled report now checks default max records value
Resolved in Pega Version 7.1.8
When scheduling a report definition, the default value for max records to export was ignored when run by a scheduled task agent but used if the report was run manually. This value is normally set to 10,000 in the system settings and should be the default unless an override value has been entered for "Maximum Number Of Rows For Export" on the Data Access tab. To correct this issue, the pzRunScheduledShortcut activity has been updated to use the default if no value has been entered.