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:

• Stateful. The Object Manager does not release a stateful or cached business service that the workflow process calls if the user pauses or finishes an instance of this workflow process. The Object Manager waits for the object that called the Workflow Engine to release the cached business service. To release this business service, the caller can use methods from the Web Channel Dedicated Block Service business service.

• Stateless. The Object Manager releases a stateful or cached business service that a workflow process calls if the user pauses or finishes an instance of this workflow process.

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.

For more information, see the following.and Siebel Business Process Framework: Workflow Guide.

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.

The following table describes how the Workflow Mode property of a workflow process affects the State Management Type property.

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 affect 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.