Siebel Business Process Framework: Workflow Guide > About Workflow Process Steps and Connectors > About Workflow Process Steps and Connectors >

About Workflow Steps


You can specify properties for a workflow process step. If working in the Process Designer, some of these properties can be specified in the Properties window. If working in the Object List Editor (OBLE), properties can be specified in the WF Steps OBLE.. For reference information about workflow step properties, see Table 113.

Adding a Step to a Workflow Process

You use the Process Designer to add a step to a workflow process. Once a step is added, you can use the Properties window to define properties for the step.

In some cases, you can choose to use the WF Steps OBLE to define properties for a step. Once a workflow process is saved, a record for the new step appears in the WF Steps OBLE, where you can modify properties.

To add a step to a workflow process

  1. In the Workflow Processes OBLE in Siebel Tools, choose the workflow process to which you need to add a step.

    If the status of the workflow process is Completed or Not In Use, click the Revise button in the WF/Task Editor toolbar.

    For more information, see About the WF/Task Editor Toolbar.

  2. Right-click the workflow process record in the OBLE then choose Edit Workflow Process.

    The Workflow Designer Palette and Properties windows open along with the Process Designer. The workflow is editable. If the palette is not visible, you can display it by choosing View > Windows > Palette in the Tools application-level menu.

  3. Drag then drop the step type you need to add from the Workflow Designer Palette to the canvas.
  4. In the Properties window, enter or modify the Name property.

    When you step out of the property, the name updates on the step in the canvas. For more information, see About Naming a Process Step or Process Property.

  5. (Optional) enter a description of the purpose of the step.
  6. Define other properties for the workflow step, as necessary.

    For more information, see Reference of Workflow Step and Connector Properties.

About Naming a Process Step or Process Property

A name given to a workflow process step or a process property must be unique within a workflow process. When you create a new process step, the step's Name property is automatically populated with a name/number combination that you can change. If you change the name, the new name, including the number, must be unique from the names of the other steps in the process.

The name given automatically to a step or a connector is based on the step or connector's type. For example Business Service 0 for a business service step, or Siebel Operation 0 for a Siebel Operation step. The number given automatically in the name for a step or a connector is an integer, such as 0, 1, 2, 3, and so forth. This number differentiates instances of the same type of step or connector. For example, Business Service 0, and Business Service 1. This number, called sequence, is stored as part of the name.

Note that some symbols, such as the period (.), cannot be used in a process property name.

About Sequence Numbers in Workflow Steps

When a new step of the same type is added to the workflow, if there is no gap between the sequence numbers for the type, the next number in the sequence is used. Otherwise, the first sequence number in the first gap for the step type is the sequence assigned to the new step. Note that a gap can be created when a step is deleted.

For example, assume are five business service steps in a workflow process: Business Service 0, Business Service 1, Business Service 2, Business Service 3, Business Service 4. If Business Service 1 and Business Service 2 are deleted, the next business service step assumes the sequence number 1, and it is automatically named Business Service 1. This sequencing approach is the same for connectors.

About the Wait Step Processing Mode Property

There are performance considerations when choosing between synchronous and asynchronous for the Processing Mode property on the wait step. For more information, see About the Server Requests Business Service.

SetFieldValue and the Processing Mode

It is recommended that when SetFieldValue is used to invoke a workflow, that the Processing Mode property be set to Local Synchronous. Since SetFieldValue can occur without data being committed, setting the Processing Mode to Remote Synchronous or Remote Asynchronous when using SetFieldValue can result in Workflow running out of process, and Siebel Workflow is not able to access the process's uncommitted data.

Siebel Business Process Framework: Workflow Guide Copyright © 2008, Oracle. All rights reserved.