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.
SR-B92674 · Issue 349429
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-B94982 · Issue 343407
Check added to prevent looping on nested data flows
Resolved in Pega Version 7.4
It was not possible to create a data flow run via the UI that contained a different data flow as its primary source because pzDataFlowContainsEventStrategy is a recursive function with the potential to loop forever when one of the sub-dataflows is the same as the current dataflow. To enhance use of this function, a check has been added to prevent the function from calling itself if the sub-dataflow is the same as the current dataflow.
SR-C11188 · Issue 352704
Backwards progress restored for unsaved cases
Resolved in Pega Version 7.4
If an unsaved case was quit from the middle of a flow, "previous" was no longer working when the application was exited and a new login session was started. When attempted, the pop-up error "This action does not work" appeared. It was possible to go forward with the flow from this point, but it was not possible to proceed backwards beyond the new start point. This occurred when going back from a subflow (a) through another subflow without shapes, then into another subflow (b) when the intervening subflow had no cases, and was due to incorrect placement in the code of the needed pyCompletedSubFlowPath. This has been corrected.
SR-C155 · Issue 343722
Flow parsing modified to accommodate new DP syntax
Resolved in Pega Version 7.4
DE was generating the error "declare page parameters not supported by PropertyRef". This was traced to the PropRefPool not being able to handle the '[' character which is part of the new DP syntax; since the parsing call with this conflict is contained in the flow but is not absolutely necessary in this stage, the system will skip the parsing at this point to avoid the error.
SR-C6264 · Issue 348027
Change stage fixed for backwards compatibility
Resolved in Pega Version 7.4
After upgrade, the stage name was incorrect on change stages utility shapes. This was traced to a backwards compatibility issue with new handling in the pzChangeStage section and has been corrected.