HTML Fragment form
Completing the HTML tab

Field

Description

Select to eliminate extra space characters in the processed HTML. This can make transmission or processing more efficient. Is does not alter the appearance of the HTML when displayed in a browser.

When selected, during stream processing the way the system handles this is different for JSP streams than (deprecated) HTML streams. JSP streams replace consecutive spaces and control characters with a single space. For example: << space >><< new line >><<tab>> is converted to << space >>. Two or more consecutive space characters are replaced with a single space, except within the curly brace characters defining directives.

The best practice is to remove all line breaks and whitespace, so a stream definition like this:

<pega:choose>
   <pega:otherwise>
       Some Value
   </pega:otherwise>
</pega:choose>

becomes:

<pega:choose><pega:otherwise>Some Value</pega:otherwise></pega:choose>

Note: HTML Streams delete control characters appearing at the beginning of the rule definition and immediately after a directive, but otherwise behaves as JSPs. For example:

<< tab >>{some directive}<< tab >><< space >><< tab >>{some directive}<< space >><< space >> is converted to{some directive}<< space >>{some directive}<< space >>.

HTML stream processing copies space characters within the text of a property value and non-breaking spaces ( &NBSP;) into the processed HTML without change.

This field and the Convert to JSP button appear only when the rule contains HTML directives rather than JSP tags. The value that appears is HTML.

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 Page 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. B-20380

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. B-16304

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. B-22073 BUG-2066 GENTJ 10/30/06

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.

This button appears only after you save the form when the Generate For value is HTML and this rule is created by a Save As operation. See Converting from directives to JavaServer Page tags.