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

Invoking Data Validation Manager from a Workflow


This task is part of Process of Invoking the Data Validation Manager Business Service.

You can invoke the Data Validation Manager business service from a workflow. This section describes some of the possible steps you can include to enable this invocation. You may need to modify and expand on this procedure to accommodate more complex business requirements. The workflow process you create must contain the following steps:

  • Start. Initiates the process instance. When the conditions have been met, the application initiates the process instance.
  • Business Service. A step in a process in which an automated call is made to the Data Validation Manager service. A workflow process definition can have one or more business service steps.
  • End. A step in a process that specifies when a process instance is finished.

NOTE:  The workflow that makes a call to the Data Validation Service must be invoked from a runtime event. If it is invoked from a script, the script passes no record context to the Data Validation Manager. The context is passed only with a runtime event. Thus, if you try to invoke a workflow using a script, the child business component context is not passed to Data Validation Manager, so it cannot validate the data correctly.

For more information about how to create a start step, business service step, and end step in a workflow, see Siebel Business Process Designer Administration Guide.

To invoke Data Validation Manager from a workflow

  1. Create the workflow in Siebel Tools.
  2. When you create the business service step, include the following information:
    1. In the Business Service form, complete the fields described in the following table.
      Field
      Value

      Business Service

      Data Validation Manager

      Method

      Validate

    2. In the Input Arguments list, create new records to establish your Input Arguments as described in the following table.
      Input Argument
      Comments

      Active Object

      Can attain a value of Y or N. If the value is N or if this input argument is not entered into the list applet, the Business Object and Object Id input arguments must be established and cannot be NULL.

      Business Object

      The name of the business object (that is, the functional area) to which the event occurs. It is required if an Active Object has not been specified or has a value of N.

      By default, the business service uses the primary business component of the business object (if defined).

      Enable Log

      Valid options include:

      • Y - Application logs all instances when the rule set runs.
      • N - Application does not track any instances of when the rule set runs.

      For more information on the Validation log file, see To view the validation history.

      Object Id

      The row ID of the principle business component of the business object. It is required if an Active Object has not been specified or has a value of N.

      Object Search Type

      Value is View or Business Object and determines which of these two arguments is used as criteria.

      Group

      Group name to which to restrict data validation rule set selection.

      Rule Set Name

      In the Value field, enter the name of the rule set to be invoked. For more information, see To define a new validation rule set.

      If the data is valid, both the Return Code and the Return Message field remain empty.

NOTE:  If the data is invalid, in addition to filling in the Return Code and Return Message, the workflow engine also generates the generic error message Error invoking business service. This error message is an expected result of how the workflow engine treats content populated into the Error Message process property by a business service. It does not indicate that the Data Validation Manager failed.

Siebel Order Management Infrastructure Guide Copyright © 2008, Oracle and/or its affiliates. All rights reserved. Legal Notices.