The configuration property files for each modifiable form are located below. Note that there are two properties files, one for the default configuration and one for the extended configuration. By default, the extended properties files do not contain a reference to a JSP file. You can define a JSP for the extended fragment to incorporate form properties that are specific to your business. The default URL and serverContext properties have also been identified below:
Instance | Location |
|---|---|
View Customer |
and
The default The default |
New Customer |
and
The default The default |
Edit Customer |
and
The default The default |
Customer Search and Customer Select pop-up in Shopping Cart |
and
The default The default |
Product Search |
and
The default The default |
Order Search |
and
The default The default |
Order View |
and
The default The default |
Scheduled |
and
The default The default |
Creating an Extended Page Fragment
Adding a new field to the end of the default fields is best done by modifying the appropriate extended properties file. Any new fields will be displayed after the default fields. It is recommended that you use configuration layering to create extended configuration files that reside within your own application module, and point these files to the extended page fragments contained in your custom web application. This prevents your customizations from being overwritten if CSC is updated, as the configuration properties are located in your web application.
Create a JSP fragment file that provides the new field information.
Add the path of the newly created JSP file to the appropriate extended properties file. Specify the
URLandServletContextfor the appended file.Save the extended properties file.
Create a new fragment and place it in the location specified by the
URLproperty of the extended properties file. Optionally, you can edit an existing JSP fragment that has been specified in the extended properties file to include the new field information.
Note: The JSP fragments are dynamically included and the file will be compiled and executed before being embedded into the form. As such, import any necessary components into your page to ensure successful compiling.
Overriding the Default Page Fragment
You can make customizations to existing form fields such as adding a new field within or above the default field layout. It is recommended that you use configuration layering to create configuration files that reside within your own application module, and point these files to the extended page fragments within your own web application. This prevents your customizations from being overwritten if CSC is updated, as the configuration properties and JSPs are located in your web application.
Make a copy the appropriate default fragment.
Make your customizations to the copy of the default fragment. Specify the
URLandServletContextfor the web application file. Save your changes.Update the appropriate version of the
/localconfigconfiguration file to point to the new copy of the default fragment.
