Siebel Business Rules Administration Guide > Integrating Rules with Siebel Runtime Events > Scenario for Using Rules to Validate Data at Runtime >

Configuring and Activating the Runtime Event


You must associate the Service Request Validation - PreWriteRecord, Service Request Validation - WriteRecord, and Service Request Activity - PreWriteRecord rule modules with runtime events.

To configure a runtime events to invoke rules

  1. From the Site Map in your Siebel application, choose Administration - Runtime Events > Action Sets.
  2. In the Action Sets applet, add a new action set. Use the following guidelines to enter its fields:
    Field
    Guideline

    Name

    Service Request Validation - PreWriteRecord Action

    Active

    Checked (TRUE) by default.

    Enable Export

    Checked (TRUE) by default.

  3. In the lower Actions applet, add a new action. In the lower More Info form applet, use the following guidelines to enter its fields:
    Field
    Guideline

    Name

    Service Request Validation - PreWriteRecord Rules

    Action Type

    Required. Select BusService from the pick list.

    Sequence

    Required. Enter 1.

    Active

    Required. Checked (TRUE) by default.

    Start Date / End Date

    Null by default.

    Business Service Name

    Enter Business Rule Service (case sensitive).

    This business service executes a rules module. It is seed data in your Siebel Repository.

    Business Service Method

    Enter RunRules (case sensitive, no space).

    Business Service Context

    Enter Service Request Validation - PreWriteRecord, the name of the rule module that this action executes.

    NOTE:  The rule module name must match the rule module name in HaleyAuthority. The comparison is case-sensitive and space-sensitive.

     

  4. Click Events in the link bar. In the resulting Events applet, add a new event record to which you associate the action set you created. Use the following guidelines to enter its fields.

    For more information about implementing runtime events, see Siebel Personalization Administration Guide.

    Field
    Guideline

    Name

    (optional) Enter Service Request Validation - PreWriteRecord Event.

    Sequence

    Required. Enter 1.

    Object Type

    Required. Select BusComp from the pick list.

    Object Name

    Required. From the list of values, select Service Request, the top-level business component.

    Event

    Required. Select PreWriteRecord.

    Subevent

    no entry necessary

    Conditional Expression

    no entry necessary

    Action Set Name

    Required. From the list of values, select Service Request Validation - PreWriteRecord Action, the action set that you defined in Step 2.

  5. Save the event record.
  6. Repeat Step 1 through Step 5 to create the first WriteRecord event. Make duplicate entries, with the following exceptions:
    • Action set Name: Service Request Validation - WriteRecord Action
    • Action Name: Service Request Validation - WriteRecord Rules
    • Action Business Service Context: Service Request Validation - WriteRecord
    • Event Name: Service Request Validation - WriteRecord Event
    • Event: WriteRecord
    • Event's Action Set Name: Service Request Validation - WriteRecord Action
  7. Repeat Step 1 through Step 5 to create another PreWriteRecord event. Make duplicate entries, with the following exceptions:
    • Action set Name: Service Request Activity - PreWriteRecord Action
    • Action Name: Service Request Activity - PreWriteRecord Rules
    • Action Business Service Context: Service Request Activity - PreWriteRecord
    • Event Name: Service Request Activity - PreWriteRecord Event
    • Event Object Name: Action
    • Event: PreWriteRecord
    • Event's Action Set Name: Service Request Activity - PreWriteRecord Action
Siebel Business Rules Administration Guide Copyright © 2007, Oracle. All rights reserved.