Add Custom Processors to the Workflow

Once you have either created a new Step Processor or Launch Step Processor or extended the existing versions, you must add the custom Processor to the workflow before an end user can access them.

Caution If you upgrade to a new Panagon Web Services version, you must redeploy all existing custom Step and Launch Processors (for additional information, see the Deploying a Custom Java Step or Launch Processor procedure).

If you add the Step Processor or Launch Step Processors while Designer is running, the new processor is not available until the next time you start Designer. Stop Designer before adding custom processors. (Refer to Configure step processors in the Management tab of the Configuration Console help for more information on adding Step Processors or Launch Step Processors to a workflow.)

The steps for adding a custom processor differ very little between HTML (ASP) and Java processors. The primary difference is that for applets hosted in ASP and HTML Step Processors and Launch Step Processors, you need not specify the package in the Class Name field.

Note Perform the following steps on a client system that can connect to the Web WorkFlo server on which you installed the modified .JAR file.

Add a custom processor by performing the following general steps:

  1. Connect to your eProcess Server, and open the Configuration Console.
  2. Log on to the proper region. Locate and select the router associated with the region.
  3. Highlight the router name, and right-click the highlighted name. Select Properties.
  4. From the Isolated Region Properties dialog box, select the Step Processor Info tab.
  5. Click add and enter the following step definition information:
  6. Click OK, and commit the changes.
  7. Close Configuration Console.
  8. Open Designer. The newly added Step Processor or Launch Step Processor should display as one of the available Step Processor options.