Symptoms

There seems to be a bug where some rules take precedence over others in their order of execution. I have a form with an advanced condition and some checking of the Forms Validation. I would like the Forms Validation to be triggered first, so that any missing fields will flash up as missing, prior to getting to the advanced condition about whether the values are valid (i.e. fall within the correct ranges). However, after setting the rule to be: "if the Form passes validation (configure) and an advanced condition is true" and saving the form, when I reopen it, it always re-organizes itself to be: "if an advanced condition is true and the Form passes validation (configure)" 

Diagnoses

We asked the client to add form validation, and then add the rule Continue to next execution and then add the advanced condition. Form validation is taken as a secondary command because it has to validate all the fields that are selected on the configuration step. The advanced condition usually takes precedence because it validates whatever data you have added. This is by design and not a bug

Resolution 

The below workaround was used

 - On the rules page the client added form validation,

 - then added the rule Continue to next execution,

 - then added the advanced condition.