Siebel Business Rules Administration Guide > Implementing Rules in Siebel Workflows >

Scenario for Using Rules in a Siebel Workflow to Do Batch Processing

This topic provides an end-to-end example in which a Siebel workflow is configured to do batch processing of Opportunity records. The process generates a comment in the Sales Objective field when the lead quality and probability of the opportunity meet an inconsistency threshold.

The process is run with the mobile Web client running against the sample 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 and the business logic 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
2. Defining the Business Process Flow
3. Specifying Invocation Requirements

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

4. Creating the Workflow
5. Adding Business Logic
6. Testing the Rule Module in HaleyAuthority
7. Deploying and Activating Rule Modules
8. Providing Calls to the Rules Engine
9. Testing the Workflow in Simulation Mode
10. Deploying, Activating, and Administering the Workflow

NOTE:  This example does not leverage output from rules to do branching in the workflow. To do such branching in a workflow, do similar configuration as is shown in Scenario for Using Rules to Provide Dynamic Navigation in a Siebel Task.