This section contains information describing the structure and operation of both the HTML Step and Launch Step Processors and the Java Step and Launch Step Processors samples. Additionally, this section includes general information on customizing the existing samples.
Within the context of Panagon Web WorkFlo and WorkFlo Services, the terms "Step Processor" and "Launch Step Processor" have specific meanings, as follows:
Step Processor: This applet or application processes the information and resources a workflow participant needs to complete a step in a workflow. When a workflow participant opens a work item, the Step Processor displays the instructions, Content Services or Image Services attachments, current field values, response options, or other resources necessary to allow the participant to process the step. When designing or customizing a Step Processor, you must account for data and information gathered prior to calling the Step Processor. In other words, a typical Step Processor will receive information from another, prior Step Processor.
Launch Step Processor: This is a more specialized type of Step Processor. Launch Step Processors begin or launch the workflow. Typical Launch Step Processors contain all of the information necessary to initialize the workflow. Launch Step Processors are independent of the condition of the workflow progress, so you need consider only what information the launch step will introduce into the workflow.
The Step Processor and Launch Step Processor samples included in the Panagon eProcess Toolkit represent a close approximation of the Processors as they are implemented in Panagon Web WorkFlo. (In the case of the HTML processors, the toolkit files are the actual Step Processor and Launch Step Processor modules, components, and files implemented in Web WorkFlo.) While you can reuse these samples in a web-based application, these Processor samples are not meant to be the only starting place for workflow development. Rather, these samples represent only one way of developing applications that can launch workflows or process steps in a workflow.
To modify the Step Processors or Launch Step Processors you must first know how to use the eProcess APIs. In fact, one helpful way of looking at Step Processors and Launch Step Processors is to view them as specialized applications that make extensive use of the eProcess APIs. The sections in this guide discussing how to modify the HTML- and Java-based versions of the samples assume that you have some understanding of the eProcess APIs and how they are used.
Panagon Web WorkFlo includes two sets of Toolkit files, depending on the development focus, for understanding and modifying Step Processors and Launch Step Processors:
HTML Processors: the HTML Step Processor and Launch Step Processor Toolkit files are installed on the Panagon Web WorkFlo server during installation.
Java Processors: the Java Step Processor or Launch Step Processor Toolkit files are included on the Panagon Web WorkFlo and Toolkit CD. (Refer to Install Panagon eProcess Toolkit for additional information.
Note The Java and HTML Step Processors support a Read-only mode. This mode opens when an end user only has Read-only permission on a work queue in which the work object is located. The user is notified of the Read-only mode when the Step Processor opens. However, in Read-only mode any changes a user makes are discarded. Additionally, while in the Read-only mode the Step Processor interface displays only the following options: Cancel, Status (if the workflow definition allows), and Help.