Conditions and Actions
Conditions and Actions
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.
Conditions and Actions are scripts or Component Object Model (COM) objects that implement your business logic. These scripts are contained in the following action table fields:
- Condition
- Action
- Compensating Action
The preceding fields can contain inline script, calls to script functions in a global script file, or the programmatic identifiers (PROGIDs) of custom COM objects. To indicate to the workflow engine what combination of scripts and objects to use, set the flags in the last column of the action table row. The Flags field represents a binary OR'd value of CdoWfTransitionFlags constants. The following table shows the possible combinations.
| Flags | Condition | Action | CompensatingAction |
|---|---|---|---|
| 0x00 | Script | Script | Script |
| 0x01 | Script | Object | Script |
| 0x02 | Object | Script | Script |
| 0x03 | Object | Object | Script |
| 0x04 | Script | Script | Object |
| 0x05 | Script | Object | Object |
| 0x06 | Object | Script | Object |
| 0x07 | Object | Object | Object |
Note In most cases, the condition field should not be empty. If you leave the field empty, and you use the ProcessDefinition object to define your workflow, you will receive an error when the ProcessDefinition validates the ActionTable. Also, the workflow engine must find at least one TRUE condition per state and event type in your ActionTable, otherwise it returns the CDOWF_NO_CONDS_MATCHED failure code.
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.