Required eProcess Services Components

Since much of Panagon Web WorkFlo operates within the Panagon Web Services architecture, when developing for eProcess Services you must reuse the contents of the following directories, which are part of the eProcess Services directory structure:

The following directories are optional only if you are creating a new user interface and supply equivalent user interface components:

Refer to the Panagon eProcess Services Architecture topic for more detailed information on the server configuration. Additionally, you should not modify the core files for the HTML Step processor or the Launch Step Processors. (Refer to the HTML Processor Toolkit Overview for more information.)

When developing for eProcess Services you will, in all likelihood, be adding new directories and files. You can reuse the modules, images, and style sheets available in the directories listed above. However, you must use all of the files in the root directory (as they were shipped), except for the following:

You can modify the files listed above according to need. If you create your own web application, the start page must be at the same level as the home.asp file. The default.htm, index.htm, and index.html files all contain <META> redirection commands to home.asp. If you want to keep the home.asp and you have created a different top level page for your web application, then you must change the redirection command to reference your new page.

Note For more information on developing for eProcess Services, which includes the client-side, JavaScript-based API objects, refer to Locate the Panagon Web Services Toolkit Help for help in familiarizing yourself with the Panagon IDM toolkit.