SR-C10909 · Issue 352697
Handling added for null OfflineCaseAttachment source
Resolved in Pega Version 7.4
An exception was being generated on each offline mobile-sync with the tracer message: "Unable to load data page D_pzOfflineCaseAttachments. Required parameter LinkRefFrom cannot be blank." This occurred when the required parameters for D_pzOfflineCaseAttachments DP were not populated. To address this, D_pzOfflineCaseAttachments DP has been changed to the pyGetAllOfflineAttachments activity, and handling has been added to exit if the parameter is empty.
SR-C573 · Issue 346166
Sync error page retains uploaded changes
Resolved in Pega Version 7.4
After changes were made to a case offline and the case was then uploaded after the case had already been reassigned to someone else, a Pega-Work-OfflineSync work object was created and a copy of the case data was placed on the embedded pySyncErrorCase page but the changes were missing. To fix this, the pzStoreAndForwardProcessItems function has been modified to ensure the changes from the uploaded version are present on the pySyncErrorCase page.
SR-C6870 · Issue 349625
Performance improvement for finishAssignment sync
Resolved in Pega Version 7.4
Analysis of a trace on the output related to a finishAssignment sync found a second read of the work object within the pzDataSyncPackageCases activity (after it was previously read in pzCheckLockingMode). In order to improve performance, the system will make use of the existing open work object to avoid the dual DB read.
SR-C7706 · Issue 350556
Performance improvement for WorkID sync
Resolved in Pega Version 7.4
In order to improve performance, changes have been made to the pzStoreAndForwardProcessItems and pzGetAllOfflineWorkIDs activities: these will populate skipDPOfflineWorkIDsInteraction to conditionally skip the DP packaging, in order to ensure the offline temp ID reconciliation does not populate the data D_pzOfflineWorkIDs twice during delta sync.
SR-B78040 · Issue 334019
Shape-retrieval logic updated for nested proxy flows
Resolved in Pega Version 7.4
A complicated proxy flow with nested subprocesses was hanging when 'next' was clicked. This was traced to getPreviousShape failing to get the correct shape due to the nested configuration, and has been fixed by modifying the logic in the getPreviousShape and hasPreviousShape methods used by process_flow.js to find the correct shape.
SR-B84173 · Issue 339408
Fixed intermittent Bulk Transfer failure
Resolved in Pega Version 7.4
Bulk Transfer action was not working for some cases in a flow which applied to an embedded data class, resulting in nothing showing up when attempting to 'transfer' those cases. This was caused by bulk transfer running the "pyTransferAssignment" flow action on the flow's applies to class (i.e., embedded data class); that flow action calls "pyTransferAssignment" section which is present in "@baseclass" which would run on the top page. In case of bulk transfer, this top page would be the flow's applies-to class, causing failure in cases using "Data-Party" flows. To correct this, the system will call the top page FA for embedded pages.
SR-B86382 · Issue 338235
Added check to prevent pxFlow page corruption
Resolved in Pega Version 7.4
The code in Work-!ReassignToWorkBasket assumed that if the property pxFlow existed then newAssignPage.pxFlowName must also exist, and went on to use the pxFlowName as a subscript to set several properties on the pxFlow page. If pxFlow existed but as an empty Page Group, there was no pxFlowName and the pxFlow page group ended up with a corrupted work object. This has been fixed by adding an additional check for the pxFlowName on newAssignPage. If the flow name is empty, the property will not be set.
SR-B88128 · Issue 338448
CompletedSubFlow paths fixed for final shapes
Resolved in Pega Version 7.4
The function getPreviousShapeFrompxFlow was not accounting for the last shape in a flow being a completed subprocess, instead skipping over it and returning the second-to-last shape instead of opening the subprocess and returning the last shape. In the mobile app, clicking on the Next button caused the application to hang and show a busy indicator. This was an issue with pyCompletedSubFlow paths not being handled properly in process_flow, and has been fixed.
SR-B91500 · Issue 340402
Flow action label not reset after local action
Resolved in Pega Version 7.4
After creating a flow action where the ID and short description were different, after the local action was launched and then closed the Flow action short description displayed as expected but the Flow action label displayed the ID instead of the short description. In this case, when a local action is launched the ProcessAction activity triggers the PerformPreProcessing activity, but that activity was passing TaskIndex as Empty. This was causing the Current Action Label to be set to empty, and a check has been added to avoid that condition.
SR-B91547 · Issue 338584
Fixed CheckFlowDependecies zOS compatibility
Resolved in Pega Version 7.4
In activity Work-.pxCheckFlowDependencies, the generated SQL's 'where' clause had constant as left operand and column as right operand with like as operator. This caused a compatibility issue with zOS/DB2. To resolve this, the the constant and column operands have been swapped in a 'where' clause with like as operator.