IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing business processes > Create business rules > Create a rule group

Use rule set names in a rule group

Each operation in a rule group contains a rule logic table, which maps a set of date ranges to a rule set or decision table. To avoid confusion, it is always a good practice to use rule set and decision table names which are unique within the operation. If the same name is used twice, it is more difficult to see that there are actually two different rule logics.

For example, suppose you have one rule set to calculate the default discount rate, and another to calculate the discount rate during a holiday period. These could be placed in different folders, with different namespaces, as follows:

If you reference these rule sets within a single operation, only the local name for the rule set is shown, so the references may appear identical in both the tool and the Web environments.

A situation where using the same rule set name might be confusing.
Label Name
Default getDiscountRate
July 1 to August 31 getDiscountRate

To avoid this problem, you should give each rule set a more descriptive name, as shown here:

If you do this, the names will be unambiguous, and there will not be any confusion.

A situation where the rule set names makes sense.
Label Name
Default getDefaultDiscountRate
July 1 to August 31 getHolidayDiscountRate

Create a rule group


Related concepts:
Rule group editor


Related tasks:
Specifying the rule logic for a rule group
Scheduling rules using the rule group editor
Customize algorithms for date and time selection
Create custom selectors