This documentation is archived and is not being maintained.

Workflows Overview 

A workflow is a set of elemental units called activities that are stored as a model that describes a real-world process. Workflows provide a way of describing the order of execution and dependent relationships between pieces of short- or long-running work. This work passes through the model from start to finish, and activities might be executed by people or by system functions.

Workflow Runtime Engine

Every running workflow instance is created and maintained by an in-process runtime engine that is commonly referred to as the workflow runtime engine. There can be several workflow runtime engines within an application domain, and each instance of the runtime engine can support multiple workflow instances running concurrently.

When a workflow model is compiled, it can be executed inside any Windows process including console applications, forms-based applications, Windows Services, ASP.NET Web sites, and Web services. Because a workflow is hosted in process, a workflow can easily communicate with its host application.

The following illustration shows how workflows, activities, and the workflow runtime engine are all hosted in process with a host application.

Workflow structure inside host application

For more information about workflows, see Developing Workflows and Developing Workflow-Enabled Applications.

See Also

Footer image
Send comments about this topic to Microsoft.