This topic describes how to modify, in general terms, the following core shared files used by the default HTML Step Processors and Launch Step Processors. In all liklihood, you will not need to modify most of these core files; in the following sections, an asterisk (*) following the file name indicates a file you are most likely to modify. This topic does not include the server-side include file, which are located in the same directory at these files.
Caution You can add new functions or extend the existing function in these files; however, you must not delete or alter the existing functions.
Similar to the stepElementInit.asp file. The file includes the following Web WorkFlo helper files:
The file uses the JiGlue COM Bridge to work with VWAttachment objects in WorkFlo Services. Refer to this file to determine how to create and access attachments that can be viewed in workflow processing.
Like the stepElementInit.asp file, the launchStepElementInit.asp implements server-side VBScript functions and client-side Javascript functions for determining and initializing system field values for the user interface components.
Additionally, the file uses the Web Services client-side, Javascript, IDMWSC_Result object to implement a Javascript switch structure. Refer to Locate the Panagon Web Services Toolkit Help for more information on using the Panagon Web Services components.
Includes the following Web WorkFlo helper files:
Refer to the file to examine the remaining referenced and included files.
The launchStepProcessor.asp file is a top-level page. The file implements VBScript functions for parsing XML step element strings composed by on the client system. Additionally, the file includes a template for the XML schema being used to parse the launch step element string and includes a description of the assumptions. For reference purposes, the well-formed XML schema is listed here:
<step> <comment>...</comment>
<subject>...</subject>
<wfId>...</wfId>
<selResponse>...</selResponse> -- Optional reponses
<att>
<name>...</name>
<isArray>0</isArray> -- 0 = non-array, or 1 for array.
<idmAtt>
<name>...</name>
<desc>...</desc>
<type>...</type>
<lib>...</lib>
<libType>...</libType>
<id>...</id>
</idmAtt>
... -- one or more IDM attachment
</att>
<att>
... -- One or more attachment objects
</att>
<field>
<name>...</name>
<desc>...</desc>
<type>...</type>
<value>...</value>
<isArray>...</isArray>
</field>
<field>
... -- One or more field
</field>
<workgroup>
<name>...</name>
<participants>...</participants>
</workgroup>
<workgroup>
... -- One or more work groups
</workgroup> </step>
Several other files (like stepProcessorAttHelper.asp, stepProcessorFieldHelper.asp, and stepProcessorWGHelper.asp) help to parse the XML string.
Includes the following Web WorkFlo helper files:
Refer to the file to examine the remaining referenced and included files.
The stepElementInit.asp page implements VBScript server-side functions for retrieving step element properties used to populate the client-side components.
Additionally, the file uses the Web Services client-side, Javascript, IDMWSC_Result object to implement a Javascript switch structure. Refer to Locate the Panagon Web Services Toolkit Help for more information on using the Panagon Web Services components.
Includes the following Web WorkFlo helper files:
Refer to the file to examine the remaining referenced and included files.
The stepProcessor.asp file is a top-level page. The file implements VBScript helper functions for retrieving and restructuring XML step element strings. The implemented functions assume that an VWSession object already exists.
The file includes a template for the XML schema being used to parse the step element information. The full XML schema is shown in the launchStepProcessor.asp file description (above).
The stepProcessorAttHelper.asp file implements server-side VBScript functions for parsing the XML string generated on the client system and saving the property information contained in the Content Services or Image Services attachment (<idmAtt>...</idmAtt>) tag set of the well-formed XML string.
The file uses the JiGlue COM Bridge to work with VWAttachment objects in WorkFlo Services.
<att>
<name>...</name>
<isArray>0</isArray> -- 0 = non-array, or 1 for array.
<idmAtt>
<name>...</name>
<desc>...</desc>
<type>...</type>
<lib>...</lib>
<libType>...</libType>
<id>...</id>
</idmAtt>
</att>
Note The full XML schema is shown in the launchStepProcessor.asp file description (above).
The stepProcessorFieldHelper.asp file implements server-side VBScript functions for parsing the XML string generated on the client system and changing the system field property information contained in the (<field></field>) tag set of the well-formed XML string.
<field>
<name>...</name>
<desc>...</desc>
<type>...</type>
<value>...</value>
<isArray>...</isArray>
</field>
Note The full XML schema is shown in the launchStepProcessor.asp file description (above).
The stepProcessorWGHelper.asp file implements server-side VBScript functions for parsing the XML string generated on the client system and changing property information contained in the work group (<workgroup></workgroup> tag set of the well-formed XML string.
<workgroup>
<name>...</name>
<participants>...</participants>
</workgroup>
Note The full XML schema is shown in the launchStepProcessor.asp file description (above).
The toolbarHelper.asp, working with the step.js file, defines the toolbar button behaviors. The toolbarHelper.asp file calls the toXML() method defined in the step.js file to generate an XML string, which is sent from the client to the server.