SR-129312 · Issue 198553
Corrected HTML display of characters in reply emails
Resolved in Pega Version 7.1.8
HTML characters were appear in the email body and subject for outbound reply messages. For example, if subject is test, the reply email would display the subject as RE: test<%gt; An HTML reply to an HTML email did not contain these entities/artifacts. Reply emails can now be configured to use HTML format, and the 'HTML' option has been added to the Message Type drop-down on the Response tab of Service Email rule.
SR-132880 · Issue 201431
Design time clarification for radio button configurations
Resolved in Pega Version 7.1.8
Previously, it was possible to configure an on-click event on a radio button in a repeating grid. This configurability was an error - although it was possible to set it up, the actions would not actually fire as intended due to the way the radio buttons work. In order to remove confusion, the actions tab for radio buttons has been removed from design time and checkboxes should be used if on-click actions are desired.
SR-130352 · Issue 199182
Corrected Microsoft Internet Explorer error for opening harness in a popup
Resolved in Pega Version 7.1.8
Configuring a button click to launch a harness in a pop-up with the Microsoft Internet Explorer 11 browser caused the error "Internet Explorer cannot display the webpage." The cause was an errant space included in the pega.u.d.url for this browser, and the GenerateHarnessHTML and GenerateLayout RUFs have been updated.
SR-131217 · Issue 199744
Stopped unexpected trigger caused by attaching note with gadget
Resolved in Pega Version 7.1.8
Declarative rules were being fired every time a note was attached to a work object using the "Notes" gadget (not advanced notes link). To fix this, the pxAttachNote activity has been updated to not trigger the declarative chaining in this scenario.
SR-131269 · Issue 200188
Fixed Harness buttons and screen resize issue
Resolved in Pega Version 7.1.8
Harness buttons were not fixed, and the screen was resizing to unviewable height on changing to screen layout. To resolve this, CSS changes have been applied to the pzbase-browser - CSS and pzbase-ie9 - CSS files to include selector for dynamicContainer div inside workarea div in not size to content mode. The rule applied is position: absolute.
SR-117083 · Issue 176581
Added sorting and filtering to work item AssignedTo and Status fields
Resolved in Pega Version 7.1.9
An enhancement has been added to allow for filtering and sorting the list of assignments at the bottom of a work item by the 'Assigned To' and 'Status' fields.
SR-128383 · Issue 193256
Child class assignments carried for bulk processing
Resolved in Pega Version 7.1.9
While processing the assignments from the Bulk Actions, the class of the parent work object was applied to child class assignments. This generated a 'Flow Action not found' error. This has been corrected so when the flow action sets a property value, it is setting the value at pyWorkPage instead of the page list item while processing the Child class assignments.
SR-130216 · Issue 202688
AssignActions modified to correctly ResumeFlow from sub-user
Resolved in Pega Version 7.1.9
If two flow actions were defined on a particular assignment in a flow that used WHEN rules to affect visibility in a sub-user's workflow, ResumeFlow was not correctly picking up the flow after the sub-user performed an action and closed the workflow. This was caused by the AssignActions state persisting instead of repopulating and continuing the flow, and the RUF 'FindAssignment2' has been modified to handle this correctly.
SR-132494 · Issue 201073
Exposed 'style' parameters for Workbasket and Operator dropdowns
Resolved in Pega Version 7.1.9
The ShowAllOperators and WorkBasketGadget out-of-the-box controls defaulted to in-line styles even when alternate styles were provided. To correct this, 'style' is now an exposed parameter for both Workbasket and Operator dropdowns.
SR-132896 · Issue 202844
Added handling for customized flows using "different work item" subprocess
Resolved in Pega Version 7.1.9
After upgrade, customized flows using the "different work item" choice on the subprocess for calling work flow from embedded data page work objects generated the error "'On Another Work Item' was specified yet the same object was supplied." This was traced to a missing pzInsKey for this use case, and the LaunchFlow RUF has been updated to handle this customization.