Support for nested logic within Flows
As a CR admin, when i want to set up a Flow with some consistent rules but 1 or 2 properties that might be different, I currently have to repeat the consistent rules multiple times (see screenshot).
It would save a lot of time, if i was able to nest logic in the following way:
he platform also doesn’t support nested logic (in this case nested OR statements), where you could group conditions like:
(Original URL = '/test/' OR '/test2/' OR '/test3/')
AND
(Topic = 'Copper' OR 'Coal')
AND
(CR Available = True)
Instead, each combination has to be built out individually, which is repetitive and time consuming. I am about to produce this configuration for around 20 different Flows, and the above would probably save me 1-2 hours of time.
Tom Ford
shared this idea
We plan on releasing a suite of Opal tools in H2 to improve the CR onboarding and maintenance experience. One Opal tool would be dedicated to management of flows, which would make it easier to create flows for the use case described. Whilst this doesn't reduce the number of flows (so complexity remains the same), they will become easier to manage via Opal. We will revisit nested logic after the Opal tools are released.
