| Platform SDK: Exchange 2000 Server |
[This is preliminary documentation and subject to change.]
Your action table rows contain three fields which implement your business logic.
These fields can contain inline script, calls to script functions in a global script file, or custom (COM) objects. You tell the workflow engine what combination of scripts and objects are in an action table row by setting the Flags in the last column of the action table row. The Flags field represents a binary OR of CdoWfTransitionFlags constants. The following table shows the possible combinations.
| Flag Value | 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 get an error when the ProcessDefinition validates the ActionTable. Also, the engine must find at least one 'TRUE' condition per state and EventType in your ActionTable, otherwise it returns a failure code CDOWF_NO_CONDS_MATCHED.