Bookshelf v8.1/8.2: Workflow Process

A workflow process allows you to use a familiar flowcharting interface to define the business processes that your company uses. A workflow process includes one or more process steps, such as start steps, subprocesses, decision points, and tasks.

Table 262. Properties of the Workflow Process
Property	Description
Auto Persist	If TRUE, then this workflow process is persistent.
Business Object	Specifies the name of the business object that this workflow process references. Optional. The drop-down list for this property displays only business objects that include a primary business component.
Effective End Date	Specifies a date that Siebel CRM uses to retire this workflow process. For example, you can set the start date to a future date and set the end date for the existing version to the same date. Siebel CRM uses the new version starting on this date.
Effective Start Date	Specifies a date that Siebel CRM uses to start using this workflow process.
Error Process Name	Specifies the name of a workflow process. If the workflow process on which you specify the Error Process Name property encounters an error, then it runs the workflow process that you define in this property.
Group	Specifies the name of a group. This group allows you to group similar workflow processes according to your criteria, such as all the workflow processes that support a particular business process. To define this group, you use the List of Values view in the Application Administration screen in the client. This property only applies to workflow processes before Siebel CRM version 7.7. Starting with version 7.7, it is recommended that you do not use this property. You can use the Project property instead.
Name (R)	Specifies a name for this workflow process.
Pass By Ref Hierarchy	If TRUE, and if this workflow process is a subprocess of another workflow process, then Siebel CRM uses a reference to send any modifications it makes in this workflow process to the parent workflow process. This property can reduce the amount of memory that a workflow process requires because Siebel CRM sends data through a reference instead of sending a value.
Process Name	Specifies a name that describes the work that this workflow process performs.
Replication Level	Specifies how Siebel CRM synchronizes this workflow process with a Mobile Web Client. You can use one of the following values: All. Synchronize this workflow process to all Remote users and to all regional nodes of the Siebel Server. Regional. Synchronize this workflow process only to regional nodes. None. Do not synchronize this workflow process.
State Management Type	For more information, see State Management Type Property of a Workflow Process.
Status	Displays the current status of this workflow process.
Version	Displays the version number of this workflow process. The default version is 0. Siebel Tools increments this version number by one each time you revise this workflow process.
Web Service Enabled (O)	If TRUE, then Siebel CRM exposes this workflow process as a Web service and can independently call it. Setting this property to TRUE does not automatically implement the workflow Web service. Defining the workflow process for a Web service does not set this property to TRUE.
Workflow Mode	Specifies the mode that defines the runtime configuration of this workflow process.

State Management Type Property of a Workflow Process

The State Management Type property specifies the type of business service request that Siebel CRM sends while this workflow process runs. A stateless business service does not depend on a state that is specific to the business service. You can set this property to one of the following values:

Every business service that this workflow process instance calls must be stateful or stateless.

The session state for the Object Manager requires a business service to contain a state management type. You must define a business service as Stateless or Stateful, or as a business service that the the Siebel Server manages.

How the Workflow Mode Affects the State Manage Type

Siebel CRM sets the State Management Type property of a workflow process to Stateful, by default It does this to preserve the behavior for releases that occur earlier than Siebel CRM 8.1. If a workflow process runs through Web Channel, then it might be necessary to modify the State Management Type to Stateless to take advantage of the session pooling that the Object Manager provides. For more information about Web Channel, see Siebel Web UI Dynamic Developer Kit Guide.

Table 263 describes how the Workflow Mode property of a workflow process affects the State Management Type property.

Table 263. How the Workflow Mode Affects the State Manage Type
Workflow Mode	State Management Type	Description
Service Flow	Stateless	A service workflow process cannot contain a user interact step or wait step. Siebel CRM runs the entire workflow process before the Object Manager can release the session back to the session pool.
Interactive Flow	Stateless	An interactive workflow process can move between sessions through the Universal Inbox. The State Management Type property is relevant only if the workflow process runs through Web Channel. An interactive workflow process runs in a user interactive session so the State Management Type does not effect the behavior of an interactive workflow.
Long Running Flow	Stateless	The Workflow Engine allows a long-running workflow process to run between sessions even if the user pauses this workflow process. It is recommended that you do not define a long-running workflow process to call a stateful business service because Siebel CRM loses the state of this business service if the instance of a long-running workflow process moves from one user session to another user session.
7.0 Flow	Stateful	Do not modify this setting unless you are sure none of the business services that the workflow process calls directly or indirectly is a stateful business service.

Siebel Object Types Reference		Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.