Hi,
I have built a workflow for an approval process with a loop: if the Approver disapproves, the Author has to make changes and then the Approver has to approve again.
I want the state transitions to be triggered based on metadata: the Approver checks a field called "I disapprove" and the Author checks a field called "Here's a new version to approve again" (very simplified explanation).
Since both state transitions are "automatic", M-Files won't save the workflow because of the possibility of an infinate loop. Even though I prevented this possibility via some rules in the Metadata Card Configuration.
Is there some way to bypass this unjustified infinate loop error without setting state transitions as manual actions?
To elaborate: the M-Files "infinate loop check" seems very primitive: you can't even build a looping workflow where transitions between state A and B (and back) happen automatically after 1 year
