SR-118190 · Issue 172520
Drag and drop work reassignment corrected
Resolved in Pega Version 7.1.7
An error was found that prevented the ability to drag and drop a request from workbasket to worklist or from worklist to workbasket in the Case Manager portal. This has been corrected.
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.
INC-102005 · Issue 556731
Child case ID prefix preserved
Resolved in Pega Version 8.4.2
When configuring a case as a child case in App Studio, the case ID prefix was cleared out of the field on the Settings tab for the case type. Investigation showed that when the child case was added to the parent case in App studio, pzaddcasetypetoapp was called but the parent activities did not pass the CaseID parameter of the child case type. This caused the CaseID prefix of the child to be null and displayed as blank in the Settings and Application. This has been corrected by ensuring the system will get and set the parameter value.
INC-119754 · Issue 561523
Corrected 'when' rule context for GetCaseDetails
Resolved in Pega Version 8.4.2
The Pega REST API Get Method /cases{CaseID} failed if the Child Case was set with Manual instantiation using a 'when' rule. This was traced to the 'when' rule being resolved using @baseclass instead of the class of the case type, and has been resolved by updating the pzGetCaseDetails activity to evaluate the 'when' rule on the case page.
INC-120608 · Issue 573001
Temporary case creation from Cosmos resolved
Resolved in Pega Version 8.4.2
Creating a temporary case in Cosmos Portal was not working. Investigation showed that the pySkipCreateHarness and pyCreatesTemporaryObject properties were not populating properly on the D_StartingFlows data page, which was traced to the way openSelectedColumns API handles non-exposed columns. To resolve this, the system has been updated to use the openEngine API for opening starting flows if the pySkipNewHarness or pyCreatesTemporaryObject property values are null.