Share via


Default and Ad Hoc Process Definitions

Default and Ad Hoc Process Definitions

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

You can specify whether new workflow items use a default workflow process or an ad hoc workflow process. There are four ways to define processes:

  • A client uses the default workflow process in a folder.
  • A client chooses from one of many processes installed in a folder. In this scenario, the process definition must be hidden to prevent unintended editing or viewing.
  • A client chooses a process definition from another folder. This requires that ad hoc workflow be enabled. Ad hoc workflows can run only in Restricted Mode. In this scenario, the process definition must be hidden to prevent unintended editing or viewing.
  • A client submits an item with an embedded process definition. This requires that ad hoc workflow be enabled. Ad hoc workflows can run only in Restricted Mode.

Default Process Definition

In a default process workflow, all documents in a workflow folder follow the same process definition. In this case, the process definition is stored at the folder level. Every new document created in that folder inherits a URL to the default process definition for that folder. To implement this type of process definition, set the https://schemas.microsoft.com/cdo/workflow/defaultprocdefinition property on the OnSyncSave registration item in the workflow folder.

A workflow enabled folder with a Default ProcessDefinition that controls all of the ProcessInstances in the folder

Client-Specified Process Definition

A client can specify one of many process definitions installed in a folder, depending on the class of document, or the client can specify a process from another folder. For example, you might have different classes of documents that have different approval behaviors. You use a relative URL to specify the process definition (for example, MyProcessDesign1.wdm). To specify a process from another folder, you must set the CdoWfAdhocFlows Enum flag directly with the Exchange store schema property. This is part of the event sink registration. Ad hoc workflows can run only in Restricted Mode.

Ad Hoc Process Definitions

In an ad hoc workflow process, the user decides how a document should be routed for review when the user saves the document. To implement this type of ActionTable, set the https://schemas.microsoft.com/cdo/workflow/adhocflows property on the OnSyncSave registration item in the workflow folder. Ad hoc workflows can run only in Restricted Mode.

A workflow enabled folder with Ad Hoc ProcessDefinitions.

Send us your feedback about the Microsoft Exchange Server 2003 SDK.

Build: June 2007 (2007.618.1)

© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.