Customizing Process Specific DEFAULT and User-Defined Web Pages

Date:17 December 2001
Product/Release:LANSA for the Web
Abstract:Caution should be exercised when creating and using process specific Web pages
Submitted By:LANSA Technical Support
Last Review:November 2010

LANSA for the Web allows you to customize HTML pages to be process specific.

The naming convention is:

<process name>_<page identifier>

Where <process name> is the name of the process and <page identifier> is the name of the page you want to customize for the process.

However: 

Caution should be exercised with any user-defined process specific DEFAULT_<pages> after an upgrade or EPC is applied as those DEFAULT pages may have been modified.

It is user responsibility to ensure that the DEFAULT changes are incorporated into the user-defined process specific DEFAULT pages.

Examples of shipped DEFAULT pages which can be customized:

DEFAULT_CONTENT       Default Process Content 
DEFAULT_FRAMESET      Default Frameset 
DEFAULT_HIDDEN        Default Hidden fields 
DEFAULT_INDEX         Default Process Menu page 
DEFAULT_LAYOUT        Default Layout 
DEFAULT_SCRIPT        Default Script Page bsp;

Example:

If a process was called PAYROLL, the process specific default pages would be created as:

PAYROLL_CONTENT       Default Process Content 
PAYROLL_FRAMESET      Default Frameset 
PAYROLL_HIDDEN        Default Hidden fields 
PAYROLL_INDEX         Default Process Menu page 
PAYROLL_LAYOUT        Default Layout 
PAYROLL_SCRIPT        Default Script Page 

Note: All process specific pages are automatically exported with the LANSA process definition. These pages do not have to be registered as Web components. This applies to both DEFAULT_pages and user defined pages.