Adding New Workflow Types: Procedures

This example describes how to create a workflow type that adds the current date to the end of a workflow name in the Content Server Title bar and runs a callback script before the corresponding workflow is initiated.

To add a custom workflow type to the custom module:

1. Orphan WFMain:WFRoot:WFCustomScriptPkg in your custom module's OSpace, and name it WFCustomScriptPkg.

2. Create a child of the WFCustomScriptPkg object, and name it CustomWorkflowTypes.
   This object contains the information required to create custom workflow types.

3. In the Globals object, run the BuildOSpace() script.

4. Override the following scripts:
   • CBExecute()

   • GetWFTypeName()

   • GetWFTypes()

   • StartWF()

You have created the objects necessary to add a workflow type to Content Server. Now you must provide the code required to perform the custom operations.

Because the WFCustomScriptPkg object is a superclass object, it may contain many child objects. If you want a particular custom operation to be performed by only one of those child objects, you can use the handled variable. When a custom operation needs to be performed, the child objects of the WFCustomScriptPkg object are passed the information in order. When the handled variable is set to TRUE, the operation was performed successfully; otherwise, the information is passed to the remaining child objects.