Unable to use Actions on a Child Item
We are creating a sub case and routing it onward. When the recipient wishes to act upon the item, via a Flow action or Local action, we get the following error "Local actions are available only when you are performing the assignment". They're in the perform harness, so in theory that shouldn't matter. Anyone have a tip to overcome this?
I saw the article at https://pdn.pega.com/support-articles/local-actions-are-not-available but I didn't see that applying to us in this case. It doesn't matter where in the flow we are, we get the same issues.
Pegasystems Inc.
IN
How are they performing actions in Child item? Is it through navigation rule in Parent itself or they are opening the child and still facing this issue ?
Wellcare
US
I've tried the Action menu and adding a button that will call a Local Action. On the Action menu I've tried adding them directly to the Navigation menu as well as a Case Wide Local action on the Case. All of these options give the same result.
Pegasystems Inc.
IN
This usually comes due to assign page mismatch. Can you confirm if newAssignPage corresponds to the correct child's assignment when you are hitting local action button?
Pegasystems Inc.
US
Hi Chris,
In your button config, you are calling a Local Action. I believe that the Local Action UI will replace the current screen. Is that right?
Can you try to launch a modal dialog (calling Local Action -> select Target as "Modal Dialog") instead of replace the current screen? i.e. to display the Local Action in the modal window.
Thanks,
Susan
Wellcare
US
The Modal Dialog was the first thing I tried actually as the Add Attachment works that way, and yes we can use these ones that are throwing the error in a Modal dialog. Unfortunately that doesn't meet our requirements for the business, we really need the full screen replace. Any idea why one would work and not the other?
Pegasystems Inc.
US
HI Chris,
Can you check the below pdn article? It may provide some help.
thanks,
Susan
Wellcare
US
That looked promising. Unfortunately, I checked out pyWorkPage though and the pyFlowName property is there and has the correct value, so there must be something else. On a side note, we found out this error applies to all Flow Actions, not just the Locals.