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.
SR-129597 · Issue 199328
Added handling for newline character in mail subject line
Resolved in Pega Version 7.1.8
A NPE was being generated by SafeURL if there was a newline character in the subject line of an attached email. The code has been updated to remove the newline characters from the subject and unfold the subject to one line.
SR-129611 · Issue 197287
Corrected CheckPrivilege function in BulkAssign
Resolved in Pega Version 7.1.8
The RUF pxCheckPrivilegeInWorkClass (called from OpenAndLockWork) was changing the name of the newAssignPage, causing downstream failure of pzBulkProcessItems. The error occurs when a Bulk Transfer operation is performed and the user does not have the proper Role, resulting in a call to the canPerform Access When Rule that then led to pxCheckPrivilegeInWorkClass changing the name of the step page. To fix this, the parameter will be assigned to the "newAssignPage" or primary page in the OpenAndWorkLock activity.
SR-129687 · Issue 195885
Updated locale clock handling for Java 7 and PAL
Resolved in Pega Version 7.1.8
Java 7 changed how locales are handled, and the two different NumberFormat classes within PRPC were sometimes leading to errors including blocking access to PAL. In particular, the way PAL set wall clock time was not compatible, and the system has been updated to parse it correctly with the new format.
SR-129690 · Issue 197180
BIX extracts made consistent independent of run method
Resolved in Pega Version 7.1.8
The property format outputted by BIX was different when BIX was run via the command line versus running it from an extract rule in the application's user interface UI. This was traced to running from the UI the batch requestor as unauthenticated and properties created in application rulesets not having property information: the XML page did not have pxObjClass set, hence the property info was null and formatting was ignored. To resolve this, the current requestor will be used (which is properly authorized), and If it is null, then a new app requestor will be created.
SR-129714 · Issue 198126
Added ability to access operator with deleted division/org
Resolved in Pega Version 7.1.8
When an operator as associated with a division and that division was deleted, the existing operator record could not be opened in the developer portal due to a validation error (in this case, associated with a missing division). While there are validation checks associated with deleting organizational units and divisions that safeguard against deletion, it was still possible to delete a non-empty division directly. When this occurred, the operator ruleform could not be opened due to being in an invalid state. Handling for this has now been added, and an operator record can be opened in DS even if the corresponding org/org unit/div has been deleted.