Siebel Order Management Infrastructure Guide > Data Validation Manager > Process of Invoking the Data Validation Manager Business Service >

Invoking Data Validation Manager from a Runtime Event

You can invoke the Data Validation Manager business service from a runtime event. When the specified runtime event occurs, the application invokes the business service. To invoke the business service from an event, you first define the event in the Administration - Runtime Events view. For more information on runtime events, see Siebel Personalization Administration Guide.

This task is a step in Process of Invoking the Data Validation Manager Business Service.

To define a runtime event to invoke the Data Validation Manager

1. Navigate to Administration - Runtime Events > Action Sets.
2. In the Actions Sets list, add a record and complete the necessary fields.

   Some fields are described in the table that follows.

   Field	Comments
   Action Type	Specifies the type of action. Select BusService.
   Sequence	Number describing the order in which the action occurs. Execution begins with the action with the lowest sequence number. Actions with the same sequence number are executed in random order. Actions occur in sequence until all actions are completed.
   Active	Check the box to indicate whether the action will be triggered or not. Inactive actions are ignored when the event occurs. This is a quick way to turn off an action without changing the start and end dates.

3. In the More Info form, complete the fields using the values described in the table that follows.

   Field	Value	Comments
   Business Service Name	Data Validation Manager	Name of the business service to invoke, if the conditional expression evaluates to TRUE and the type is BusService. Enter the value exactly as shown.
   Business Service Method	Validate	Method to invoke on the business service. Enter the value exactly as shown.
   Business Service Context	Example: "Rule Set Name", "Validation", "Enable Log", "Y" These input arguments are equivalent to those presented in Step 2.	Name-value pairs to specify the inputs to the business service method. Both the name and the value must be enclosed by quotation marks and separated by a comma and a space after the comma.

   CAUTION:  Failure to use the syntax specified in the Business Service Context field may result in errors.

4. In the link bar, click Events to associate an event with the action set.
5. In the Events list, add a record and complete the fields as described in the table that follows.

   Field	Comments
   Name	Optional. Select an event alias from the drop-down list. Selecting a name automatically populates the Object Type, Object Name, Event, and Subevent fields. This is based on the event template created in the Event Aliases list. For more information on creating event aliases, see Siebel Personalization Administration Guide.
   Sequence	Required. An event can trigger multiple action sets. Enter numbers in this field to control when the action set associated with this event in this record executes relative to other action sets associated with this event.
   Object Type	Required. Select BusComp from the drop-down list.
   Object Name	The name of the application, business component, or applet (depending on the object type) to which the event occurs.
   Event	Required. Select from the drop-down list. The choices depend on which object type you choose. Valid values include: Use the PreWriteRecord business component event if you want to control whether a record can be written to the database, based on the outcome from the validation. Use the PreDeleteRecord business component event if you want to control whether a record can be deleted from the database, based on the outcome from the validation.
   Action Set	Required. Select an action set to run when the event occurs. The Name name is defined in the Action Sets view tab. For more information, see Step 3.

6. Either close down and relaunch the server or mobile clients, or select Reload Runtime Events from the applet menu.