Hi Ajay,
I have tried to create a flow like yours using Designer RCP POC (a lightweight version of 9.7) against IS 9.5 SP1.
I can see the variable y in the second map step.
When the condition on the label of the sequence is not matching, the sequence is simply skipped.
If this is not desired you will have to add more sequences under the branch for the other conditions and handle them accordingly.
Exit on Failure will only fire when a step in the sequence fails.
The depicted code does not contain a step which can fail currently.
Most likely this is used as a sort of Try-Catch-mechanism:
SEQ (EXIT on SUCCESS)
- SEQ (EXIT on FAILURE; Try-Block)
– signals success when all steps have completed successfully
– signals failure as soon as one of the steps fails
- SEQ (EXIT on DONE, Catch-Block)
– always signals success
The outer sequence exits if either the first inner sequence has been completed (the second sequence is then skipped) or if the first sequence fails after the second sequence has been completed.
Regards,
Holger
#Flow-and-Java-services#webMethods#Integration-Server-and-ESB