Many of the ASP files you create for your Process application may need to use some or all of the Process Java Applets Connectivity (PJAC) for FileNet Web Services ASP and JavaScript files in the <drive> ...\Program Files\FileNet\IDM\Web\IDMWS\Redist\WF_Extras directory on the FileNet Web Services server. Normally, you should not need or wish to modify any of these files.
The following table summarizes the PJAC for FileNet Web Services files (or file sets) you are most likely to reference in your Process applications.
Referenced file |
Description |
---|---|
WF_Extras\Attachment.js |
Provides client-side functionality for viewing an attachment in its native application or in the IDM Viewer. Called by Attachment.asp (see next item). Both the Attachment.js and the Attachment.asp files use the FileNet Web Services JavaScript objects extensively. For information on these objects, see FileNet Web Services Files Referenced by Process Applications. |
WF_Extras\Attachment.asp |
Implements the server-side functionality for viewing attachments. |
WF_Extras\globalInfo.asp |
Provides Process router and FileNet Content Services port numbers. Additionally, this file specifies the FileNet-supplied and custom .JAR file locations needed for both default and customized Java applets. |
WF_Extras\verifySession.asp |
Provides the ability to verify Process session (VWSession) information. |
WF_Extras\Token.js | Provides client-side functionality for retrieving the session token for the current session. |
WF_Logon\isPWLogon.asp |
Provides the ability to get Process session (VWSession) information for Step Processors and Launch Step Processors currently in session via the FileNet Web Services server. If no session exists, this file provides the ability for the user to be prompted to log on to the appropriate Process session. |
PWRedirector.asp |
Provides a means of retrieving session information from FileNet Web Services for the current Process session. The PWRedirector.asp file, which resides in the root directory, redirects remote calls to the proper pages in the Process application. Note If the user does not start from the root web directory of the FileNet Web Services server, many of the Process application-scoped variables used in PJAC for FileNet Web Services will be either unavailable or NULL. This requirement to start in the root directory is particularly important for email notifications for Step Processor and Launch Step Processor applications. |
WF_Launcher\open_launcher.js | Must be included in any file that launches a Launch Step Processor. See workflow_main.asp for usage. |
WF_Step\open_step.js | Must be included in any file that launches a Step Processor. See workflow_main.asp for usage. |
WF_FileOpen\FileOpen.js |
Implements client-side functionality for opening and working with attachment files retrieved from FileNet Content Services or Image Services libraries; activated from the Step Processor toolbar. These scripts use the FileNet Web Services JavaScript objects extensively. Any file referencing these files must handle events associated with the IDMWSC_Event object (see Event.js description in FileNet Web Services Files Referenced By Process Applications). |
WF_FileOpen\FileOpen.asp |
Implements the server-side functionality for opening and working with documents from the Step Processor toolbar. These files are called by the corresponding .JS files on the client (see previous item). |