Modify the HTML Launch Step Processor

This topic describes how to customize the default HTML Launch Step Processor to meet unique workflow requirements.

While no Integrated Development Environment (IDE) requirement for ASP development exists, these procedures assume you are using Visual InterDev and that you have a solution already set up similar to the one described in the Developing for ASP section of this guide. An alternative to using Visual InterDev is working directly in the <drive>...\Program Files\FileNET\IDM\Web\IDMWS directory structure on your Web WorkFlo server. If you know ASP development requirements and you want to make minor changes to specific files, working in the directory structure might be the best solution. The primary disadvantage is you will be working in an active web server directory structure, so mistakes are hard to correct.

Caution The HTML processors are designed to reuse some shared files, which are located in the \WF_Html_Toolkit directory. Do not modify the files in the \WF_Html_Toolkit directory. Modifying the shared files might cause problems with Step Processor and Launch Step Processor shipped with Web WorkFlo.

Customize the default HTML Launch Step Processor by performing the following steps:

  1. Create a new directory under the \Redist\WF_Launcher directory (at the same level as the \HTML directory). If you are using Visual InterDev, you can add a new Folder.
  2. Name the directory according to the function of the processor. (This procedure will use the directory name \new_HTML_Launcher.)
  3. Copy the contents of the \Redist\WF_Launcher\html directory - including the images directory - into the \new_HTML_Launcher directory.
  4. Rename the launcher_main.asp file to newlauncher_main.asp. If you are not using Visual InterDev, you must change the file attribute from Read-only to Read/Write.
  5. Open the newlauncher_main.asp file.
  6. Modify the .ASP files as needed. (Refer to the HTML Launch Step Processor Relationships topic for more information on launch processor file dependencies and the frameset implemented in the file.)
  7. If you need to modify any of the files in the \WF_Html_Toolkit directory, copy the needed files into the directory you created for your new processor.
  8. Change all references to the file(s) in the modified processors.
  9. Add the Launch Step Processor to the workflow. (Refer to Configure Step Processors in the Management section of the Configuration Console help for more information on adding Launch Step Processors to a workflow.)
  10. Test your new Step Processor pages from your application development server.

Note You might want remove image files you know you will not be using, copy only those image file you are sure to use, or add image files to the \Images sub-directory in your new directory structure.

User Interface Modifications

The default launcher_main.asp file includes the colorOpt variable for controlling the default color of the Launch Step Processor tabs.  The default colorOpt value is a hexadecimal value of "#669966" (corresponding to a RGB color model). The variable is passed to the tab.asp, tabContent.asp, and stepInfo.asp files.