SR-118738 · Issue 172565
Handling corrected for drag and drop image attachments from Outlook
Resolved in Pega Version 7.1.7
If a document containing an image was added to a work object from Outlook via drag and drop, it would be corrupted when opened. This was caused by an encoding/decoding mismatch - the encoding differed depending on whether the file was first saved to the desktop or not, but the decoding did not take that into account. This has been corrected.
SR-94370 · Issue 119519
AddChildWork updated to allow child case creation from step flows
Resolved in Pega Version 7.1.7
When attempting to create nested sub cases for rows in a page list with a Split for Each sub flow by calling the pyCreateSubCases flow, an error was generated. There was a workaround of using a utility shape to call pxAddChildWork instead of a split for each calling pyCreateSubCases, but pxAddChildWork has been updated in order to allow creating child cases using the step page as the primary page and not always defaulting to pyWorkPage.
SR-113396 · Issue 162534
Smoothed background Bulk Processing processing
Resolved in Pega Version 7.1.7
If the setting for BPUnitsToProcessForeground is given as 0 in all cases, attempting to run Bulk Processing in the background failed and logged an "Index out of bound" exception in the system logs. To cover this condition, a check has been added to handle zero items in the foreground processing when running background Bulk Processing.
SR-113919 · Issue 170809
Made page displays consistent between Java versions
Resolved in Pega Version 7.1.7
"pxflow" pagegroup values in pywork page were being placed differently depending on the version of Java used in the environment. This was caused by a handling error in situations where there is no classname, and has been fixed.
SR-114882 · Issue 164513
Validation error display corrected for screen flow harness
Resolved in Pega Version 7.1.7
Inconsistencies were appearing in the error display on the harness of the screen flow. The issue was due to the "Allow errors" value being set to true even when "Save on last step" was unchecked. While there was a workaround of unchecking both "Allow errors" and "Save on last step" options, this has been fixed.
SR-117855 · Issue 171394
Resolved NPEs during case creation
Resolved in Pega Version 7.1.7
If a null pointer error was generated during the case creation process, all subsequent records being processed also generated the error. This issue occurred when adding and later removing work party data, and was found to be related to a stack trace not being generated for the reported issue and an attempt to index a change to a page that's no longer available. To correct this, a code change now handles the condition which caused the NPE (writes an index for a non-existent page and then skips it) then logs information for analysis.
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.