Why is our local action messing with our Screen Flow?
Hello.
Here is the situation:
We've got a Screen Flow and we need to also have local actions available all along the course of this Screen Flow.
They have been added to the Sections (associated to the Flow Actions that are used in the Screen Flow) using buttons which are launching "Local Action" in Modal windows.
Problem: whenever such an local action is used, Pega is apparently unable to get back to the initial Flow Action the local action was launched from. As the local action is displayed in a modal, once it is submitted we're indeed back on the initial Flow Action but... as soon as we try to perform anything, we're only getting a "The Operation completed successfully, but returned no content" screen.
Any idea how to have local actions available in a Screen Flow) and not messing with it?
Thanks.
Accepted Solution
Pegasystems Inc.
FR
So here is the explanation: the Local Action was messing with the Screen Flow because... in the Local Action post-Activity there was a "Call CreateWorkPage" step. Once this call has been moved "somewhere else, out of the post-Activity" (but not in the Pre-Activity as it was trigerring the same issue) the Screen Flow was able to perform alright again after the Local Action was used.
NB: the call to CreateNewPage wasn't messing with the pyWorkPage as the right parameter was set.
So basically I found out the issue but.. I can't explain why it was an issue to begin with. In my humble opinion, it shouldn't be an issue but factually it is.
Pegasystems Inc.
FR
Hello,
I don't think you will be able to correctly work with ScreenFlows with such scenario.
Why don't you just work with a fake screen flow instead. Keep your screen flow appearance but just use a normal one.
Accepted Solution
Pegasystems Inc.
FR
So here is the explanation: the Local Action was messing with the Screen Flow because... in the Local Action post-Activity there was a "Call CreateWorkPage" step. Once this call has been moved "somewhere else, out of the post-Activity" (but not in the Pre-Activity as it was trigerring the same issue) the Screen Flow was able to perform alright again after the Local Action was used.
NB: the call to CreateNewPage wasn't messing with the pyWorkPage as the right parameter was set.
So basically I found out the issue but.. I can't explain why it was an issue to begin with. In my humble opinion, it shouldn't be an issue but factually it is.