Pass data in to this node from a Data Query node and apply a condition to it to execute a child node or branch.
Use as many Decision Branch nodes in your runbook as you need, but be careful to avoid creating branches that produce contradictory, redundant, or confusing results. The Runbook Editor will not prevent you from defining unproductive branches.
Each Decision Branch node requires at least one child node or branch. This can be either the True path or the False path, but, for clarity and consistency, it's a good practice to define both paths, even if one is only a stub.
The Decision Branch properties are context-sensitive, based on the data forwarded by the immediately preceding node.