Siebel Business Process Framework: Task UI Guide > Creating Steps and Connectors >

Creating a Siebel Operation Step

A Siebel operation step is a type of task UI step that performs an operation on business component data. Example operations include Insert, Update, and Query. Siebel CRM runs a Siebel operation step, and then the Siebel Operation Object ID process property stores the row ID of the record where Siebel CRM performed the operation. If the query operation returns multiple records, then the property stores an asterisk (*).

You can create a Siebel operation step for a business component that references the same business object that the task UI references. To update a business component that does not reference this business object, you must use Siebel Tools to configure the business component to reference the business object.

Some business component fields are not available for modification. For more information, see Business Component Fields That a Task UI Can Modify.

To create a Siebel operation step

1. Add a Siebel operation step to a task UI.

   For more information, see Adding a Step to a Task UI.

2. In the Properties window, set the Operation property.

   If you must configure Siebel CRM to update or insert a field that includes dependencies, then make sure the field is valid. For example, if your task UI updates the area and subarea fields of a service request, then you must make sure the value that the user chooses for the subarea field is valid for the area field. For more information, see Siebel Business Process Framework: Workflow Guide.

3. In the Business Component property, choose the business component where this Siebel operation step uses data.
4. If you must configure Siebel CRM to create a field, or if the Siebel operation step performs an insert operation, then make sure you add the field to the Siebel operation step.

   For more information, see Identifying the Business Component Field for a Siebel Operation Step.

5. Optional. Create a search specification for the Siebel operation step.

   For more information, see Defining the Context for a Task Step.

6. Optional. In the Multi Value Property Window, add input arguments and output arguments.

   For more information, see Creating an Output Argument on a Task Step.

About the Defer Write Record Property

Setting the Defer Write Record property to TRUE on a Siebel operation step allows the user to provide data for a required field in the subsequent task view step before the Siebel operation step attempts an insert. If the user attempts to provide data for a Siebel operation that already occurred, then Siebel CRM displays an error that a required field includes no data. This situation occurs when the following logic exists in your task UI:

1. A Siebel operation step performs an insert operation.
2. Task view step follows the Siebel operation in Step 1. The user uses this task view step to provide the data that the insert requires.

To fix this problem, the Defer Write Record property defers the insert operation until a commit operation occurs that allows the user to provide the required data before Siebel CRM does the insert operation. The Defer Write Record property is not specific to a task UI. For more information, see Using the Defer Write Record Property When You Disable Task Transaction and Siebel Object Types Reference.