 |
 |
|
|
|
Using the Process Open Client Out-Of-The-Box HTML Processors
FileNet Process Open Client provides a complete fully-functional set
of "out-of-the-box" (OOTB) HTML Step and Launch Step Processors.
These Processors are hosted by .NET Web Forms which are provided to the
client in response to an HTTP request. The .NET Web Forms comprise the
ASPX pages and their associated VB.NET-based code-behind files, which
are available for customization.
Subtopics include:
OOTB
HTML Processor ASPX Pages
The following OOTB HTML Processors and their associated code-behind files
are available for customization (these are all located in the eprocess
directory or one of its subdirectories; the default location is \Program Files\FileNet\IDM\Web\FNOpenClient\eprocess):
OOTB HTML File |
Default Directory Location |
Description |
FnProcessMain.aspx
|
\FNOpenClient
|
Top-level ASPX page and its associated .aspx.vb code-behind
file for the out-of-the-box HTML Personal Work Manager (PWM). This
is the main ASPX page for Process.
|
FnWFLauncher.aspx
|
\FNOpenClient
|
Top-level ASPX page and its associated .aspx.vb code-behind
file for the out-of-the-box Workflow Definition Launcher (launches
a workflow definition).
|
FnStepProcessor.aspx
|
..\FNOpenClient\eprocess\StepProcs\HTML\OOTB
|
Top-level ASPX page and its associated .aspx.vb code-behind
file for the out-of-the-box HTML Step Processor.
|
FnLaunchProcessor.aspx
|
..\FNOpenClient\eprocess\Launchers\HTML\OOTB
|
Top-level ASPX page and its associated .aspx.vb code-behind
file for the out-of-the-box HTML Launch Step Processor.
|
Customizing
the OOTB HTML Processors: Basic Procedure
When customizing the OOTB HTML Processors, use the following basic procedure:
- Copy the existing OOTB top-level ASPX page and its code-behind .aspx.vb
file to an appropriate directory on the FileNet Web server. You may
create this directory within the Process Open Client Web Footprint directory
structure (for example, the \Program Files\FileNet\IDM\Web\FNOpenClient\applications
directory or its user-selectable equivalent directory) or whereever
it is appropriate.
- Rename the copied file (most developers prefer to use a name associated
with the function for that step; for example: LoanOfficerApproval.aspx
and LoanOfficerApproval.aspx.vb).
- Open the ASPX file in your IDE or text editor. If you are not using
Visual Studio, you will need to change the file attribute from Read-only
to Read/Write.
- Customize the ASPX file, its code-behind .aspx.vb file, User
Controls, and if needed, the FnProcessSessionDP Data Provider
according to your business requirements. Customization can range from
relatively simple changes that modify the "look and feel"
of the OOTB HTML Step Processor to more complex changes that modify
the layout and controls for specific business logic requirements, to
even more extensive changes involving content integration, accessing
different data sources, modifying access (for example, by hiding controls),
making authentication changes, and so on.
Use the Process-specific Open Client VB.NET-based User control .ascx
files and their associated .ascx.vb code-behind files to customize
the Processor's user interface. You may use these controls in conjunction
with Control Factory controls and the .NET server controls (and associated
.NET classes) to provide the presentation layer (the "View"
part of the MVC model) that provides the user interface. Open Client
User controls (the file names are fairly self-explanatory) include
controls for attachments, plugins, a base User control class (FnStepProcBaseUC.ascx),
data fields, general info, milestones, reassignments, workgroups,
and so on.
For details on customizing the OOTB HTML Step Processor, see Developing
a Custom HTML Step Processor. For details on customizing an HTML
Launch Step Processor, see Developing
a Custom HTML Launch Step Processor. For general guidelines on
creating/modifying ASPX pages, see Developing
ASPX Pages for Open Client, elsewhere in this Open Client Developer's
Guide.
- Once you have completed the ASPX page, its associated code-behind
file, any User Controls you have used or modified, etc., you must deploy
your Processor on the Web server. For details, see Deploying
HTML Step Processors.
- Once you have deployed your application, you will need to add the
new Open Client Step Processor, or Launch Step Processor, etc. to the
workflow. For details, see Adding
an HTML or Java Step Processor to the Workflow.
|