Siebel Business Process Designer Administration Guide for Financial Services > Designing Workflow Processes > Working with Siebel Operation Steps >

Defining a Siebel Operation Step

NOTE:  After executing an Insert step, the Siebel Operation object ID process property automatically stores the row ID of the record that was created.

You can define Siebel Operation steps for any business component associated with the business object selected for the process. If you want to update a business component not associated with the business object, you can either invoke a subprocess or associate the business component to the business object using Siebel Tools.

All fields are available for update and insert except fields based on multi-value groups and calculated fields. If you want to update a field based on a multi-value group, you can define a business component for the field and link the business component to the object using Siebel Tools. An example is an update to an Account Team. Account Team is based on a multi-value group, so it cannot be updated by selecting the Account business component. However, you can create a business component called "Account Team" and then associate it with the Account business object using Siebel Tools. You could then select Account Team as the business component to update with the Siebel Operation step.

Calculated fields cannot be updated using Siebel Operations steps because typically they require values from other business component fields. Calculations should be performed using expressions.

The object ID for the process is automatically passed to Siebel Operation steps. Because this automatic passing occurs, you do not need to enter a search specification value unless you are updating child records. For example, if you have a process based on the service request object and you want to update the service request, you do not need to enter a search specification. However, if you want to update activities for the service request, you may want to enter a search specification to query the specific activity that you want to update. Otherwise, the update step updates all activities for the service request.

The object ID cannot be null if you are executing a Siebel Operation, unless you are inserting into the primary object ID. If the process has no object ID, the Siebel Operation step returns an error.

When performing a query operation for child records, the Siebel Operation Object ID process property field will return the row ID if one record matches, a "*" if multiple records match, and Null/no value if no records match.

The insert/update operation updates the Siebel Operation Object ID process property field of the record's row ID.

NOTE:  The Workflow Policy programs and Siebel Operation steps use different object layers to update data. For example, you may have a Workflow Policy that calls a Workflow Policy Program to update a Service Request Record. This method goes through the Data Layer in which State Model does not apply.

Conversely, if you have a Workflow Policy that calls a Workflow Process Action and in the Workflow Process, you have defined a Siebel Operation step to update a Service Request Record, this method goes through the Object Layer in which the State Model does apply.

To define a Siebel operation

  1. Make the appropriate process active by selecting it in the All Processes view.
  2. Navigate to the Process Designer view and double-click the Siebel Operation icon to access the details view.

    3. NOTE:  To add a Siebel Operation step to the workspace, drag and drop the Siebel Operation icon from the palette to the workspace.

  3. Enter a name for the step.
  4. Enter a description of the purpose of the step.
  5. Select the type of operation. The available choices are:
  6. Select the name of the business component.

    7. NOTE:  After you double-click Siebel Operation in the Process Designer, you must specify the Business Component Name in the Fields applet.

  7. If you need to define fields for this Siebel operation, continue to Defining Fields for the Siebel Operation.
  8. If you need to define search specifications for this Siebel operation, continue to Defining Siebel Operation Search Specifications.
  9. If you need to define output arguments for this Siebel operation, continue to Defining End Step Output Arguments.

Defining Fields for the Siebel Operation

NOTE:  If the Siebel Operation step will perform an insert operation, make sure that all required fields have been added to the Siebel Operation step. System fields and predefaulted fields are automatically populated.

To define fields for a Siebel operation step

  1. With the appropriate Siebel operation name displayed in the Siebel Operation applet of the Siebel Operation view and the Fields applet active, select Add New Record from the applet menu.
  2. Select the name of the field to be updated.
  3. Choose an input argument type. The choices available are:
  4. If the field type selected is Literal, enter a value.
  5. If the field type is a Process Property, select a property name.
  6. If the field type is a Business Component, select the applicable business component name and business component field.
  7. If the field type is an Expression, enter the expression in the value field.
  8. Enter any appropriate comments.

Defining Siebel Operation Search Specifications

You can define search specifications to identify the specific data on which to perform the operation. Search specifications are used when the business component has multiple records and you want to perform the operation on only some of the records. For example, if you have a process for the Account object and you want to update only those Opportunities with a lead quality of Poor, you would define search specifications to access only those Opportunities.

To define Siebel operation search specifications

  1. With the appropriate Siebel operation name displayed in the Siebel Operation applet of the Siebel Operation view and the Search Specifications applet active, select Add New Record from the applet menu.
  2. Select a search specification type. The choices available are:
  3. Enter search specifications.

    4. CAUTION:  Define your Siebel operation search specification as efficiently as possible, so that only the smallest necessary set of rows will match. Search specifications that select a large set of rows could cause severe performance degradation.

  4. If the search specification type is expression, select the applicable business component name.

NOTE:  A search specification of type Literal is executed as written. For example, [Status] LIKE `*Open*'. A search specification of type Expression allows you to construct a search specification dynamically. For example, "[Contact ID] = ` " + [&New ID] + " ` " will be evaluated to [Contact ID] = `1 - ABC' if the New ID process property is 1 - ABC at runtime.

Defining Siebel Operation Step Output Arguments

Output arguments allow you to store a resulting value in a process property. This value can then be passed to other processes.

To define output arguments for an operation step

  1. With the appropriate Operation step name displayed in the Operation Step applet of the Operation view and the Output Arguments applet active, select Add New Record from the applet menu.
  2. Select the property name from the picklist.
  3. Choose an output argument type. The choices available are:
  4. If the output argument type selected is Literal, enter a value.
  5. If the output argument type is Output Argument, enter the argument.
  6. If the output argument type is Business Component, select the applicable business component name and business component field.
  7. Enter any appropriate comments.

 Siebel Business Process Designer Administration Guide for Financial Services 
 Published: 22 May 2003