I have a case wide Local Action Configured on my case type.
this action should be available through Action Menu in Case in both Review mode and in perform mode. It works fine in Pega 24 but after Upgrade to Pega 25 it does not work.
I can see the action menu on case in review screen but when I click on Go to open the assign mode the Actions menu disappears and I am not able to access the local action that I have configured as case wide action.
Has anyone faced this issue in Pega 25 or what would be the workaround for this so my local action is always available on the Case.
The Action is added as Case wide Actions in Case designer.
It is configured to be always Visible.
The observation I see is that our assignment is not directly on the pyWorkPage context. It is on nested embedded Page.
so when any assignment is directly on pyWorkPage context (i.e. Problem Flow or wait shape) then these Actions are available even after we open the assignment.
In our case as our assignment is on an embedded page, the Actions are available when the case is opened for View but as soon as we click on Go to open our assignment to perform the assignment, all the Actions other than “Follow” are filtered out.
This same configuration worked fine in Pega 24, but after upgrade to Pega 25 we are seeing this behaviour.
I have tried adding the FlowAction directly as Local Action at the assignment level as well as on the containing Flow also still the action gets filtered our on load of the perform assignment screen.
Hi @VVNagaSaiN this means, We have a flow(VolumeApprovalWrapper) on the Work Page. In this flow we are calling a subflow (EachVolumeApproval) using split-for-each. This sub flow in turn contains split-for-each to run another sub flow VolumeApproval.
Our assignment shape is in VolumeApproval subflow.
in 24.2 the actions were available always. but in 25 I see that if I have an assignment directly on the WorkPage then actions are available but if I open any assingment that is defined in VolumeApproval Subflow then the action gets removed from the actions menu.
I echo with @MarcCheong. If an already working functionality is broken, there is high probability that it is a bug in the specific version. Please check with Pega support and let us know the feedback.
INC-D22633 was raised for this. and this was found to be a bug in Pega 25.1.2. That is fixed in Pega 25.1.3 version. Below explanation is provided by Pega team.
"The issue was caused by a data clearing process in the Split For Each functionality. When opening an assignment from the flow, the system was inadvertently deleting available actions (including case-wide actions like Edit details and Change stage) during the parent case panel refresh process, and these actions were not being restored.
This issue has been fully addressed in Pega Infinity versions 25.1.3 and 26.1. The fix introduces a flag called ‘skipMergeAssignmentsAndActions’ that prevents the clearing step from deleting available actions, ensuring they remain accessible on the perform screen."
