|
Siebel Business Rules Administration Guide > About Developing and Deploying Siebel Business Rules > Development Process Overview >
Adding Business Logic
This topic is a task in the process Development Process Overview. You implement rules to make decisions and, if applicable, take action. To construct rules from business logic, you first identify the actions or decisions that are the final product of the business logic, then work backward to construct the conditions to evaluate and entities and relations on which the conditions are built.
Activities |
Translate the logic requirements you derived in Specifying Business Logic Requirements into modules of rule statements, using the natural language conventions of the HaleyAuthority authoring environment.
- Write rule statements to implement the actions that are the end products of the logic; for example, set the value of a field, display a message, set an output property value, and so on.
- For each action statement, write applicability statements (conditions) that trigger the action.
- Write conditions that suffice to trigger the action individually as if applicability statements. These conditions are evaluated as or conditions.
- Write conditions that must be satisfied, independent of other conditions, as only if applicability statements. These conditions are evaluated as and conditions.
- Write conditions that negate the trigger, independent of any other conditions, as except applicability statements. These conditions are evaluated as and not conditions.
- Similarly, state conditions and exceptions that support higher level conditions.
- Write statements for assumptions, if necessary.
- Sharpen the structure of the statements in each module.
- Applicability statements supporting a higher level statement are typically easier to understand and debug than creating a complete if-then condition as one statement.
- Avoid compound conditions in an individual statement by expressing the conditions as individual applicability statements.
- Minimize negative logic.
|
For information, see: |
HaleyAuthority User Guide is the primary source of instruction on creating rule modules. Creating Rule Modules Scenario for Using Rules to Validate Data at Runtime Scenario for Validating Data Using Script to Invoke Rules Scenario for Using Rules in a Siebel Workflow to Do Batch Processing Scenario for Using Rules to Provide Dynamic Navigation in a Siebel Task |
|
