HTML Fragment form - Completing the HTML tab
|Omit extra Spaces?|
This field and the
Convert to JSP
button display only when the rule contains HTML
rather than JSP tags. The value that displays is
As a best practice, use JSP tags rather than directives. In most cases, you can convert HTML fragments that use directives to use JSP tags automatically, using the button. See Converting from directives to JavaServer Pages tags.
Do not save the rule form when the source contains both JSP tags and directives.
If this rule is circumstance-qualified or time-qualified, make this Generate For value match the Generate For value of the base rule. The base rule and the qualified rules must all use JSP tags or all use directives.
Enter the HTML, script, or CSS text. The text may include directives or JSP tags, but not both. Update the
Pages & Classes
tab to include each page name referenced in the HTML code, with the corresponding class.
Although HTML fragment rules do not have an Applies To key part, you can identify the class of a primary page on the Pages & Classes tab, leaving the Page Name field blank. After you update the Pages & Classes tab, you can reference properties on this page without identifying the page name.
Use of JSP tags in HTML fragment rules offers superior performance and other advantages over directives. Although both directives and JSP tags are supported, JSP tags are recommended for new development. Conversion of existing HTML fragment rules that use directives to functionally equivalent rules that use JSP tags is straightforward.
|Convert to JSP||
This button displays only after you save the form when the
- List View form - Understanding the HTML tab
HTML tab on the List View form
- About HTML Fragment rules
- HTML Fragment rules - Completing the New or Save As form
HTML Fragment rules
- More about HTML Fragment rules