Question
Error when Refresh-Current Harness from within a Flow Action
Hola Amigos,
From within a navigation menu, we are attempting to launch flow actions via Run Script function "pega.ui.HarnessActions.handleMenuAction". Upon launching a flow action from here, we get an error when attempting to "Refresh-Current Harness" that states:
"By performing this assignment, you are disabling stage SLA and stage/case-wide local actions for the current stage of your work object."
This only happens when we have opened the flow action via the run script above, as we cannot simply "Launch a Flow Action". Any ideas on how to resolve this issue?
Note: For the function insHandle parameter we are using ".pxFlow(pzInternalCaseFlow).pxAssignmentKey"
Thanks!
Khamaal
***Updated by Moderator: Marissa to update categories***
Thanks for the response Coher. To add some context, this action has already been completed in the business process. What we have done is added a menu to allow the user to access this assignment again, from outside of the flow. We are trying to mimic Pega's OOTB functionality for Case wide actions in our menu, and Pega is using said script. Basically, we want to re-open a flow action from outside of the flow, which cannot be done with action "Launch local Action". Any advice?
Thanks
-Khamaal
FYI, I see another post with the same issue we are experiencing. They went with the "Launch Local Action" which will not work, which is why we are using this script.
https://pdn.pega.com/community/product-support/question/problem-launchi…
Please bear with me as I am still new to Pega 7. Looks like we want to mimic the Case Wide Local Actions links, which the client wanted removed. We are trying to mimic this via navigation menu.
Why cannot you simply launch the flow action in the canonical way, instead of using a script?
It sounds as if by using the script you are bypassing some of the boiler-plate that goes into launching the flow action through flow-action command itself. Although this may be unexpected, I don't think the script-launched reaction is a bug. You're stepping outside of the standard mechanism by launching through a script, essentially saying to the system "don't worry, I will manage everything that needs to get managed." And apparently limiting the downstream actions you can take.
Returning to my original question, why not use the canonical method?