Currenlty gates can only what on dependencies or on conitions that have to be hooked manually by a user.
We would like to have a third option to open/complete a gate. We would like to add a list of (boolean) variables to a gate and the gate waits until all of them are true and then opens/completes automatically.
Regards,
Roland
by: Roland F. | 7 months ago | Templates & Releases
Comments
Could you provide further details about the use case and clarify the intended representations of these variables?
Additionally, could you explain if parallel synchronization is a part of this, and if so, in what manner?
Hi,
currently our releases contain a lot of gates that are used to give the approval for follow up steps. To reduce the complexibilty of our templates, we want to seperate the approvals from our processes.
The gates in the original templates shouldn't wait on one or more approvals/gates inside the process. Instead there should be a single gate that is waiting on all the approvals.
Our idea was that the separated approval process will be started asynchronously whenever the responsible person wants to give a speficic approval(s). After the user gave the approval(s) the approval process sets the (boolean) variables in the original template/release und the original process just waits until all the variables for the required approvals are true.