|
Siebel Business Rules Administration Guide > About Developing and Deploying Siebel Business Rules > Design Process Overview >
Determining Siebel Development Tools for Implementing the Business Process
This topic is a task in the process Design Process Overview. In this task you determine which Siebel development tools can be leveraged to implement the business process. The rules engine is one of the tools that is available. Many processes that can be implemented by using the rules engine can also be implemented using script. However, rules allow much of the logic of the process to be maintained declaratively and external to your Siebel application. Changing the logic maintained in the rules does not incur downtime because no recompiling of the Siebel Repository is needed. NOTE: This design task is not included in the examples in this document. The development tool in each example fits the business process and invocation requirements.
Activities |
In addition to invocation requirements, the following guidelines suggest Siebel development tools that fit various requirements of the business process, and aspects that may suggest implementing the rules engine:
- The user interacts in the process:
- Siebel runtime events can be used in response to specific events.
- Rules engine can be used to implement more complex tests on field values and on calculations, and can display messages for different conditions.
- Rules engine can be used to set multiple field values that are dependent on more complex criteria.
- Siebel Task UI can be used to implement multiple-step tasks that are initiated by the user.
- Rules engine allows complex decision-making and task-branching that depend on output from rules.
- Rules engine allows client-side validation based on UI events, such as entering a text field, to be embedded in the task.
- Siebel Workflow can be used to implement multiple-step tasks that can be initiated in response to events.
- Rules engine allows complex decision-making and task-branching that depends on output from rules.
- The process validates data:
- Some fundamental data validation can be implemented using business component user properties or field user properties.
- Validation of data entry by the user can be implemented with Siebel runtime events, such as PreWriteRecord, or with Siebel Workflow.
- Non-interactive data validation can be implemented using runtime events, such as WriteRecord, or with Siebel Workflow for seamless multi-step processing, such as batch processing.
- For runtime event or Workflow implementations, rules engine can be used to perform more complex decision-making and to set field values that depend on more complex criteria. With Siebel workflow, rules output can be used as criteria for process branching.
- Other non-interactive workflows, such as batch processing, can also be implemented by Siebel Workflow.
|
For information, see: |
Scenario for Using Rules to Validate Data at Runtime Scenario for Using Rules in a Siebel Workflow to Do Batch Processing Scenario for Using Rules to Provide Dynamic Navigation in a Siebel Task |
|
