The outflows would behave as configured. If we are able to create a "global condition", I would see setting gateways similar to a user task where you can choose whether to set it to a manually defined condition or use a global condition. It doesn't have to work exactly like that, but that's the idea. This way when the global condition is updated, it only affects those gateways where it is used. The outflows themselves behave the same as always, if the condition(s) are satisfied take that path.

I understand the "global condition" would handle what outflow is actually TRUE, but you would still need to wire it to something within your process diagram on each form. If something were to change either the count or order of outflows you would have to rewire each process.

With decision tables in cloud, you have to map the rule output to a form field so this would probably work as you wanted here as well so if the output name is the same it will always map to the process variable outside of it. BUT you would still need to setup the gateways to handle the task routing in each process. Is this kind of what you are looking for?

Zach, you are correct that if the count or order of the outflows needs to be rearranged than it would have to be done in each process, which I've never had to worry about to be honest.

Have you seen decision tables in cloud before? I'm curious if that type of approach fits this use case.