Siebel Business Rules Administration Guide > Integrating Rules with Siebel Runtime Events >

Scenario for Using Rules to Validate Data at Runtime

This topic provides an end-to-end example in which a runtime event is configured to invoke rules module to:

• Validate a new or modified service request record before it is written to the database.
• Auto-populate some fields.

Each of the following sections applies to one job role on the Siebel project that is responsible for completing the implementation tasks in that section.

The two job roles are:

• Business analyst or business developer. This individual is responsible for specifying the business process flow, the business logic requirements, and the UI requirements.
• Siebel configuration developer. This individual implements the requirements provided by the business analyst or business developer by performing configuration tasks in Siebel Tools, HaleyAuthority, and in the Siebel application.

The implementation process includes the following subprocesses and top-level tasks, by role.

• Design process. The tasks in this process are done by the business analyst or business developer:

1. Specifying Business Logic Requirements

• Development process. The tasks in this process are done by the Siebel configuration developer:

2. Adding Business Logic
3. Testing the Rule Modules in HaleyAuthority
4. Deploying and Activating Rule Modules
5. Configuring and Activating the Runtime Event
6. Testing Rules Modules in the Siebel Application