Remove Nested Activities from Conditional Activities
A lot my customers are enjoying logic app, but when they started using it in real life, we started seeing 'complications' during the development of the workflow.
One of the most embarrassing behaviors is the Control-Condition activity.
With this controller, we are 'obliged' to use nested workflows, which complicates the development and the graphical user experience, in addition you cannot have one activity that will 'start' for both conditions.
- In the attached picture (Picture 1, white), we can see that the nested behavior will make the UX more unpleasant (Specially if we have different levels of nesting, this will be a nightmare), and development will be too (The json code will be hieroglyphics) --> Why not making the condition like any other activity (Picture 2, green)
- Another limitation is also that we cannot run the same Activity, in both True and False iterations. Foe example, how can i run Activity Y when my condition is True ?