You can reduce the complexity and testing of large Ruleflows by breaking a Ruleflow into smaller Ruleflows, and then constructing the larger Ruleflow from them. The resulting modularity simplifies unit testing and collaboration.

You can change the name of a Ruleflow on the canvas context so that it provides meaning, and you can add comments. None of these actions change the Ruleflow properties of the original Ruleflow.

With two Ruleflows, each can be updated and tested independently, and as long as you ensure that the Vocabulary stays consistent -- separate teams can collaborate on developing their rules. That makes it easy to reuse either of these Ruleflows. For example, if pricing varies in different markets, then you can create a new Ruleflow that brings in the same risk assessment rules to provide the data to process against a modified policy pricing Ruleflow for the other market.

Note: Deploying Ruleflows within a Ruleflow - When this Ruleflow is deployed, the generated Decision Service will include the content of both Ruleflows. However, when either of the included Ruleflows changes, Ruleflows that include one of them are not automatically updated -- each must be redeployed to include the changes.

For more information, see Ruleflows .