Orchestrating business rules in a ruleflow.

Using ruleset parameters to transfer information.

Representing the business policy as if-then statements.

Packaging business logic in application code as decision service.

SOAP/XML web service

REST/JSON web service

Java Message Service (JMS)

Remote interface of an EJB rule session

DSService war

HdtsService.war

DecisionRunner.war

DecisionService.war

- Organize tax rules in a common rule project to address taxes for the states sharing the same logic

- Create a separate rule project for every state where taxes calculations are unique

- Override common rules with unique rules from this separate rule project

- Create a rule project for every state to include its own tax rules

- Package all rule projects into a single RuleApp with multiple rulesets

- Create a rule project with only the rules of one state and use these rules as the only ruleset of a RuleApp

- Create a rule project with a single decision table with all states listed and the tax logic for every state in separate virtual methods from the BOM that can be used in the table.

- Use this rule project as the only ruleset in the RuleApp.

Rewrite complex BAL rules as technical rules.

The way in which rules are written have no impact on performance.

Modify the BOM to remove the {this} placeholder to make the rules less verbose.

Make sure that conditions that test a collection of objects come before simpler conditions, to reduce the number of objects that later conditions in the rule must test.

When a snapshot is created in one of the branches

When a new ruleflow is created in one of the branches

When the same decision table is modified in both branches

When an action rule is modified from Rule Designer in one of the branches