Managing branches

Decision Designer allows branching so that you can manage the evolution of decision services over time.

Branches provide a structured way to develop and manage changes in a decision automation.

They allow multiple users to work independently without affecting the work of others, while maintaining a stable version of the decision automation. A typical workflow involves creating a branch for a specific change, sharing and reviewing updates, and merging completed work into another branch. To support governance and collaboration, you can also protect branches to control who can merge and share changes. Following a consistent branching strategy helps teams organize development work, reduce merge conflicts, and safeguard important branches.

By default, a decision automation starts with a default master branch. This default branch cannot be deleted. From there, you can create other branches to develop changes independently, then merge them back when they are ready.