Create a Custom Job

Associate a custom job with a lifecycle transition.

Two steps are necessary to create a custom job. First, an administrator adds a custom job to a lifecycle. Second, a programmer creates the job.

First, add the custom job type to a lifecycle. You must be an administrator to do this.

Click Tools > Administration > Vault Settings.
On the Vault Settings dialog, click Behaviors tab > Lifecycles.
On the Lifecycle Definitions dialog, select a Lifecycle Definition (e.g., Basic Release Process) and then click Edit. The selected definition name appears in the title bar.
From the Lifecycle States list, select the lifecycle state to edit and then click the Transitions tab.
Click Edit to open the Transitions dialog and select the Custom Job Types tab.
Click Add and enter a name in the Add to Input New Custom Job Type Name field. Click OK.

Note: A typical naming convention is to prefix your company name to any job types.

This Custom Job Type will be initiated whenever an object transitions through this lifecycle.

To enable this Custom Job on other transitions, repeat steps 3 - 5 and specify an existing Custom Job Type instead of creating a new Custom Job.

Next, a programmer creates the job (new plugins to the Job Processor). Jobs are code defined as .NET dlls; you decide what the Job does.

Note: This is intended to run as a service, so avoid UI code.

Create a .NET assembly.
Set up a procedure.
Deploy the procedure to a certain directory location.
Configure the Job Processor to find and load the extension. The next time the Job Processor runs it loads your extension.
When the Job Processor sees a Job Type that matches one your plugin can handle, the Job Processor will route the job to your plugin code.