Skip to Content
Last modified by Danniar Firdausy on 2024/09/27 09:18
From version 25.1
edited by Bouke Reitsma
on 2024/03/01 15:29
Change comment: There is no comment for this version
To version 27.1
edited by Bouke Reitsma
on 2024/03/01 15:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -19,12 +19,10 @@
19 19  
20 20  == 3. Group Deployment Step ==
21 21  
22 -== 3.1 Grouping ==
22 +To configure a Group deployment step, you need to add a new deployment step and choose Step type "Group". To configure the step more information is required. A container should be chosen for which the inbounds will be stopped. The second requirement is the **exact** name of the group that should be affected by the deployment step. An action should be picked for the selected group. For a "Group" deployment step the options are to start or to stop the inbound components within the groupname. Optionally, a description can be added.
23 23  
24 -To configure grouping, we need to open the flow designer of the flow in Create. We want to edit and enter "Start Editing" mode. On the inbound component(s) in the flow, we now have an "Advanced" tab that allows you to configure the grouping information.
24 +[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-group-deployment-step.png]]
25 25  
26 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-starting-point.png]]
27 -
28 28  {{info}}Note that the options above are available in all inbound components. The one chosen above is simply an illustration of how to configure.{{/info}}
29 29  
30 30  Once on the "Advanced" tab, you must define the group name. You can determine the group name if this is the first flow you change. In all subsequent flows, you want to add to the same group, you must use the **same** group name.