Siebel Business Rules Administration Guide > Implementing Rules in Scripts >

Scenario for Validating Data Using Script to Invoke Rules

This topic provides an end-to-end example in which a script:

• Invokes the Business Rule Service business service with an appropriate rule module
• Processes the output from Business Rule Service

The rule module contains rules that validate a new or modified account record before it is written to the database.

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. Deploying and Activating Rule Modules
4. Creating the Script
5. Testing the Rules Module