User Interface
|
Modify the basic "look
and feel" of the user interface.
|
ASPX pages, User Process and Open Client Controls, other files
as appropriate.
|
Modify the top-level ASPX page, its associated .aspx.vb
code-behind file, and other files as needed, for the OOTB HTML Step
Processor.
|
|
Change
the banner of the OOTB Step Processor.
|
FnBannerUC.ascx
|
Modify the FnBannerUC Open Client User Control.
|
|
Change
the colors of the OOTB Step Processor.
|
FnStepProcessor.aspx.vb; appropriate User Controls
|
Modify the OOTB HTML Step Processor ASPX code-behind file and the
User control whose color you want to change.
|
|
Change
the images in the OOTB Step Processor.
|
FnStepProcessor.aspx.vb; appropriate image files, .gifs,
etc.
|
Modify the OOTB HTML Step Processor ASPX code-behind file and the
image files you wish to use or change.
|
|
Modify
the page layout or structure of the OOTB Step Processor.
|
FnStepProcessor.aspx; FnStepProcessor.aspx.vb; appropriate
User Controls
|
Copy, deploy, and modify the OOTB HTML Step Processor ASPX page
and its code-behind file; use the User controls you want to add,
change, or delete (see next two items).
|
|
Add
new User Controls.
|
FnStepProcessor.aspx; FnStepProcessor.aspx.vb; appropriate
User Controls
|
Copy, deploy, and modify the OOTB HTML Step Processor ASPX page
and its code-behind file; use the Process, Open Client, Factory,
.NET or other controls controls you want to add. This may require
customizing business logic in the new FnStepProcessor.aspx.vb
and other files.
|
|
Hide
existing User Controls.
|
FnStepProcessor.aspx; FnStepProcessor.aspx.vb
|
Copy, deploy, and modify the OOTB HTML Step Processor ASPX page
and its code-behind file, removing (better than commenting out)
the existing User controls you do not want.
|
Content Integration
|
Modify content integration of the FileNet/COM API Foundation objects
or from other data sources.
|
FnStepProcessor.aspx; FnStepProcessor.aspx.vb; appropriate
User Controls; Process and Open Client Data Providers
|
Copy, deploy, and modify the OOTB HTML Step Processor ASPX page
and its code-behind file; modify the User controls as needed; modify/use
the Process Open Client and general Open Client Data Providers.
You may wish to use FileNet eForms to facilitate HTML form content
integration.
|
Build From Scratch
|
Create customer-based framework integrating custom user interface,
content, and Process.
|
FnStepProcessor.aspx; FnStepProcessor.aspx.vb; appropriate
User Controls; Process and Open Client Data Providers; Web application
server; other files
|
Either copy, deploy, and modify the OOTB HTML Step Processor ASPX
page and its code-behind file or create your own. Create new User
Controls using the Open Client Controls and the .NET Controls; modify/use
the Process Open Client and general Open Client Data Providers or
create your own (you may wish to use the Process public class Data
Provider FnProcessSessionDP to handle Process authentication,
logon and logoff (inherits FnProcessBaseDP). Requires interface
to Web application server for authentication.
|
JiGlue
Issues
|
Customizing a Data Provider.
|
FnStepProcessor.aspx; FnStepProcessor.aspx.vb; FnProcessStepProcDP
Data Provider
|
The JiGlue COM Bridge enables you to make VB.NET calls for Process
APIs with the effect of native Java statements. The FnProcessStepProcDP
Data Provider provides the interface to JiGlue. If you customize
a Data Provider, there are JiGlue-related issues you will need to
take into account (see JiGlue
Issues).
|