Siebel Business Process Framework: Workflow Guide > Options for Configuring a Workflow Process > Setting the Workflow Mode Property >

Types of Workflow Process Modes

This topic includes the following topics:

• About the Service Workflow Process
• About the Interactive Workflow Process
• About the Long-Running Workflow Process
• About the 7.0 Workflow Process

To determine the run-time behavior of a workflow process, you can set the Workflow Mode property of a workflow process to use one of the following values:

• Service Flow. A workflow process that runs a set of operations.
• Interactive Flow. A workflow process that helps the user to navigate Siebel views.
• Long-Running Flow. A workflow process that can last for hours, days, or months.
• 7.0 Flow. A workflow process that is compatible with Siebel CRM version 7.7 or earlier.

About the Service Workflow Process

A service workflow process is a type of workflow process that runs a set of operations to complete a work unit from beginning to end. A service workflow process is a transient workflow process, which is a type of workflow process that runs to completion in a short amount of time without stopping or pausing for an event or activity. A service workflow includes no special behavior. Siebel CRM can call it as a subprocess from another service workflow, an interactive workflow, or a long-running workflow, but not from a 7.0 workflow. A service workflow process includes the following limitations:

• Cannot wait for a run-time event or pause for time.
• Cannot include a user interact step or a wait step. The Process Designer does not allow you to add a user interact step or a wait step to a service workflow process.

For an example service workflow process, see Defining a Workflow Process That Creates an Activity for a Sales Representative.

About the Interactive Workflow Process

An interactive workflow process is a type of workflow process that assists and controls navigation for a user across Siebel views and screens. It includes one or more user interact steps and it typically includes a run-time event.

For an example, see Defining a Workflow Process That Creates a Service Request and Navigates the User.

For more information, see Options for an Interactive Workflow Process.

Interactive Workflow Process in a UI Context

An interactive workflow process can run only in a user session context. It cannot run in the Workflow Process Manager server component. It cannot run in a server component that does not include a user session context, such as the Business Integration Manager server component. To run in a user session context means the workflow process must run in an Application Object Manager that contains a user session context, such as one of the following Siebel CRM applications:

• Siebel Call Center
• Siebel Service
• Siebel eSales
• Siebel eService

These applications support view navigation, view display, and so on, which is necessary when using an interactive workflow because they display views through the user interact step and they require interaction with a user who clicks buttons and links.

About the Long-Running Workflow Process

A long-running workflow process is a type of workflow process that is persistent. It can last for hours, days, or months. The Send Order to External workflow process is an example of a long-running workflow process. It sends an order to a system that is external to Siebel CRM, and then waits for a reply. You can use a long running workflow process to define a single workflow process that handles an entire business process transaction that coordinates between multiple subprocesses. The Quote to Cash business process is an example where a long-running workflow is useful.

To create a collaborative long-running workflow process, you can assign a subprocess to a user. The Workflow User Event Service business service creates a user event that can span from one user or session to another user or session. For more information, see Workflow User Event Service Business Service.

You cannot use a user interact step in a long-running workflow process, but you can add an interactive workflow process as a sub process step in a long-running workflow process. You cannot use the Process Simulator to simulate a long-running workflow.

If you create a long-running workflow process, then you must use a user event and not a run-time event to start or resume the workflow process.

For more information, see Options for a Long-Running Workflow Process and Defining a Sub Process that Assigns a Long-Running Workflow Process.

About the 7.0 Workflow Process

A 7.0 workflow process is a type of workflow process that provides backward compatibility for an existing workflow process that was defined in a Siebel release earlier than Siebel CRM version 7.7. If a workflow process was defined earlier than version 7.7, and if you upgrade to version 7.7, then the existing workflow process becomes a 7.0 Flow workflow process, by default.

If you must upgrade a workflow process that was defined earlier than Siebel CRM version 7.7 to version 8.0, then you must first define the workflow process as a 7.0 workflow process. You must upgrade a pre 7.7 workflow process to version 7.7 before you can upgrade it to version 8.0.

7.0 Flow Usage

If you create a new workflow process, then it is strongly recommended that you do not use the 7.0 Flow workflow mode. If you do not define a workflow mode for a workflow process in a release that occurs prior to Siebel CRM version 8.1, then Siebel CRM assumes the mode is 7.0 Flow. If you create a new workflow process, then make sure you do not set the Workflow Mode property to 7.0 Flow so that Siebel CRM does not assume the mode is 7.0 Flow. Starting with Siebel version 8.1, if you create a new workflow process, then Siebel Tools sets the Workflow Mode property to Service Flow, by default.