1. Working with Oracle Forms
  2. Administration
  3. Creating Your Own Applet Definition Template Files

Creating Your Own Applet Definition Template Files

Consider creating your own applet definition template files (by modifying the templates provided by Oracle). By doing it, you can hard-code standard Forms parameters and parameter values into the template.

Your template can include standard text, a browser window title, or images (such as a company logo) that would appear on the first Web page users see when they run Web-enabled forms. Adding standard parameters, values, and additional text or images reduces the amount of work required to customize the template for a specific application. To add text, images, or a window title, you must include the appropriate tags in the template HTML file.

See Specifying Special Characters in Values of Runform Parameters for information about coding the serverArgs applet parameter.

Any user-added customized configuration files (such as user client registry files or user key binding files or multiple environment files) must be copied to the same directory as the corresponding default configuration file.

For example, if the user has created a French environment configuration file default_fr.env, then it must be placed in the $DOMAIN_HOME/config/fmwconfig/servers/WLS_FORMS/applications/formsapp_14.1.2/config directory.

Variable References in Template HTML Files

When a variable reference occurs within a string delimited by quotes or apostrophes (for example, the value of an applet parameter), then when the value of the variable is substituted for the variable reference, HTML escape sequences replaces the HTML metacharacters ('&', '<', '>', quote, and apostrophe).

This sequence is not done for variable references outside delimited strings. Therefore, such variables should be specified in the restrictedURLparams system default configuration parameter, for security reasons.