You are here: Reference > Rule types > Correspondence Fragments > Correspondence Fragment form - Completing the Stream tab

Correspondence Fragment form
Completing the Stream tab

  1. About 
  2. New 
  3. Stream 
  4. Pages & Classes 
  5. History 
  6. More... 

Complete this tab to define the source for the fragment, using the rich text editor in design mode or HTML codes in source mode.

(Rich text editor facilities are not available for fragments that use directives rather than JSP tags.)

Field

Description

(no label)

Enter rich text for the fragment. In design mode, a wide variety of tools are available in the toolbar including fonts, font sizes, colors, lists formatting, graphic elements and alignments. Certain controls are available only in Design mode, and only when some text is selected.

Upper toolbar

Icon

Result

(Arial)

Change the font of selected text.

(8)

Change the font size of selected text

(normal)

Convert the selected paragraph to a normal paragraph (<p> tag) or one of six heading levels (<h1> to <h1>).

Unordered list

Convert the selected paragraphs to an unordered list (<ul> tag).

Ordered list

Convert the selected paragraphs to an ordered list (<ol> tag).

Indent

Indent, increase space at the beginning of the selected lines.

Outdent

Outdent, reduce space at the beginning of the selected lines.

Make Link

Make the selected text an HTML link (<a> tag). In a pop-up window, enter the HREF= value in the Name field. Select the Open in new window box if desired. Optionally, enter ToolTip text in the Description field. Click Save.

Add Image

Insert a reference to an image. (The URL must identify an image that is available to the correspondence recipient.)

Add Property

Include the value of a scalar property at the selected insertion point. Complete the pop-up window to supply the property Name, an optional Format (control rule) and an optional When condition rule. You may type in a full property reference. Click Save.

The system generates a <pega:reference > JSP tag from the information you provide.

Include

Include the value of a section or paragraph rule at the selected insertion point.

Complete the pop-up window to identify the rule type (section or paragraph), the Purpose key part, an optional When condition rule, and (if the included rule is based on a page other than the page of this paragraph), a Using Page page name value. Click Save.

The system creates a <pega:include ..> JSP tag from the information you supply.

Lower toolbar

Icon

Result

Bold

Bold the selected text using the <strong> HTML tag.

Italic

Make the selected text italics.

Underscored

Make the selected text underscored.

Subscript

Convert the selected text to a subscript.

Superscript

Convert the selected text to a superscript.

Font color

Change the font color of the selected text. Choose a color from the palette.

Background color

Set the background color of the selected area. Choose a color from the palette.

left align

Left-align the lines in the selected paragraph.

Center

Center the lines in the selected paragraph.

Right align

Right=-align the lines in the selected paragraph.

Full align

Justify the lines in the selected paragraph by adding spaces.

Design

Switch to design mode

Source

Switch to source mode.

Spell check

Spell check the correspondence.

Omit Extra Space

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 correspondence.

When selected, at runtime PRPC:

  • Deletes control characters such as tab and newline.
  • Replaces two or more consecutive space characters with a single space, except within the curly brace characters defining directives.

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

Generate ForTypically, the system sets this field to HTML or JSP, to indicate whether the HTML source is to contain HTML directives or JSP tags. For new rules, the initial value is JSP.

Use of JSP tags offers superior performance and other advantages over directives. Although both directives and JSP tags are supported, JSP tags are recommended for new development.

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.

About Correspondence Fragment rules