This topic provides an overview of the structure of the HTML Step Processor and Launch Step Processor toolkit and describes each of the components. Since these HTML processors are based on eProcess Services architecture, you cannot modify or extend these Step Processor or Launch Step Processor samples without first understanding how to access workflow sessions, objects, elements, queues, rosters, and logs using the the eProcess APIs. Additionally, you must understand how to use the Panagon Web Services JavaScript objects to access the Content Services and Images Services servers, and how the JiGlue COM Bridge functions.
This section contains information on the following topics:
In addition, you will find reference topics on the following subjects:
Before customizing the HTML processor files, you should know how the default HTML processors operate. Once the Step Processor is initialized, the web server supplies the step element property values. The values are stored on the client system, in the client-side objects. The property values stored on the client provide the means of updating the processor information. (Storing the property information on the client system reduces the number of server calls needed to complete the workflow step.) Once the processor step element is complete, the property values are converted to a XML string. Only the XML string is sent to the server. Once the server receives the XML string, the Web WorkFlo application parses the string and updates the values in the workflow.
The HTML Step Processors and Launch Step Processors use the JiGlue COM Bridge to access the attachments in the Content Services and Image Services libraries. When the HTML Step Processor or Launch Step Processor accesses attachments, the processors use the IDM Web Services Javascript objects; therefore, the user must supply valid user credentials to access the Content Services or Image Services libraries.
The HTML Step Processor will verify URL/UNC format when the user assigns an attachment. The processor expects a URL to begin with "http://". The processor expects a UNC to begin with "file://". The processor will warn if a local file is selected with a format of "file:/c:/" (where "c" is any letter representing a drive).