If your flow action 1 is getting executed then your assignment must have moved to the next level which is not happening here . So I assume you are trying to say that when you are reaching to assignment 1 it is showing the screen of Flow action 1 by default . Am I correct ?
If this is your concern then the answer for this will be it is happening by design. When you are moving an assignment from one step to other, by default it will open up the flowaction screen which is having highest lieklihood .
Thanks for the reply. Let me explain the scenario little bit,
First, flow is not advanced through FlowAction1. When I check where am I, it's showing that flow is currently on this assingment.
And in terms of screens, before comming to this assignment which is associated with a perform harness, using an activity (show-harness method), we are showing a custom review harness.
So in screen, we are able to see that custom review harness and flow is currently on this assignment. After submit that custom review harness, screen will advanced to the perform harness which is set on the assignment and flow will still remains on the same assignment.
However the problem is, before we sumbimt that custom review harness and advanced to perform harness which set on the assignment (While we are on that custom review harness), FlowAction1 is already getting exectued.
Please reply if anything is not clear, And I think this is because of FlowActionHTML_Simple section's behaviour. Can you please advise on the purpose of that section.
You may want to carefully use the history of your work object to determine in more detail what is happening when, and why. Also, specify a PRE and a POST activity for each flow action and have those write to system log and the work object history. Is an agent, such as the SLA, advancing your flow from an independent process?
The expected behavior would be this:
1) The interactive user would see one of the two flow action screens appear, by which point the PRE activity for that flow action will have been run.
2) If the user does NOT click SUBMIT on that action, the POST activity will never run.
3) If an agent, such as your SLA, advances the flow, then the POST activity will be run.
So look at the work history log and the system log (if you put in any olog statements in your activities) to see which things actually ran and at what timestamps. /Eric