Using a Siebel Operation Step with the Object Id Process Property

When Siebel CRM finishes an Insert or Upsert operation, it stores the Row Id of the record that it created. It stores this Row Id in the Siebel Operation Object Id process property. It passes the Object Id of the Workflow Process to the Siebel operation step. It is not necessary to define a search specification unless Siebel CRM must update child records. For example, if a Workflow Process:

• References the Service Request business object, then it must update the service request but it is not necessary to define a search specification.

• Must update activity records for the service request, then you can enter a search specification that queries for the activity that Siebel CRM must update. If you do not do this, then the update step updates every activity that Siebel CRM associates with the service request.

If Siebel CRM runs a Siebel operation, then the Object Id cannot be null unless it inserts this Object Id into the primary Object Id. If the Workflow Process does not contain an Object Id, then the Siebel operation step returns an error.

The Siebel Operation Object Id process property returns the following values if a query operation modifies child records:

• The Row Id if one record matches.

• Null or no value if no records match.

• An asterisk (*) if multiple records match. It provides this result to distinguish from a value that returns a unique record or no record. Typically, a unique record matches or no records match. In most situations, multiple records do not match and Siebel CRM returns an asterisk.

The following option returns the Row Id of a matching row:

only

The Insert, Update, and Upsert operations update the Siebel Operation Object Id process property of the Row Id for the record.