Siebel Business Rules Administration Guide > Developing Siebel Business Rules > Process of Developing Business Rules >
Creating a Rule Module
This task is a step in Process of Developing Business Rules.
You implement business rules to make decisions and, if appropriate, execute logic. To build business rules from business logic, you first identify the actions or decisions that constitute the final product of the business logic, then work backward to build the conditions to evaluate and entities and relations on which the conditions are built.
To develop the business logic, you translate logic requirements identified in Specifying Business Process Logic Requirements into modules that consist of rule statements, using the natural language conventions of the HaleyAuthority authoring environment.
For important information about creating a rule module, see Rule Modules and Rule Statements.
To create a rule module
- In HaleyAuthority, navigate to the Modules and Statements View.
If the Modules and Statements tab is not available, then from the application-level menu, choose the View menu, Tabs, then the Modules and Statements menu item.
- Choose the Modules and Statements folder in the explorer, choose Object, then choose Add a module.
- Enter a name for the module.
Naming restrictions include:
- The module name cannot include special characters, such as an asterisk (*), question mark (?), slash mark (/), exclamation point (!), at sign (@), or quotes (" or ').
- The module name cannot include a Windows reserved word, such as CON, COM1, LPT1, AUX, or NUL. However, the module name can include a reserved word as a substring in the name. For example, Consulting SRs is acceptable, but Con alone is not acceptable.
- The entire module name must consist of fewer than 100 characters.
- (Optional) Add a submodule:
- Choose a module.
- From the application-level menu, choose the Object menu, then the Add a Submodule menu item.
- Name the submodule.
You can repeat this procedure to add more modules and submodules, as required.