More about Section rules

Process Commander resolves a reference in a harness rule to a section rule during stream processing, by evaluating the<pega: include > JSP tags (or include directives).

For both section rules and harness rules, the system generates HTML from information provided in the rule form as it saves the rule form. Note these important differences:

A harness rule creates a complete, well-formed HTML document, starting with the <HTML> tag and ending with the </HTML> tag. A section rule corresponds to a well formed segment of HTML text, but not an entire HTML document.
For a harness rule, you can review but not directly edit the system-generated HTML, accessed from the HTML tab. For a section rule, if the Auto-generate HTML? checkbox is cleared, you can edit the generated HTML text.

Java code display

When you save a Rule-HTML-Section rule, the system converts your HTML and JSP tags or directives to Java source code. As a learning or debugging aid, you can review this Java code.

C-1665Click the Show Java toolbar button () to see the system-generated Java code that implements the section rule. The window presents a read-only preview of the Java that implements this rule instance. This Java code is not identical to the Java that executes at runtime, which includes Java code inlined from other rule instances and reflects rules in the requestor's RuleSet list.

SmartInfo support

Section rules support the SmartInfo capability of pop-up windows. When the user holds the mouse pointer over a display element for 700 milliseconds, a pop-up window appears that can supply static or variable information in context. Most SmartInfo pop-up windows are read-only and disappear as soon as a user clicks anywhere outside the window.

Tip By default, SmartInfo pop-up windows disappear when a user clicks anywhere outside the window. To add a close box to the SmartInfo pop-up window and have the pop-up window remain until explicitly closed, include the standard section @baseclass.SmartInfoClickable within the section. (This standard section adds a close box but does not otherwise alter the appearance of the section.)
You can't use the report paging feature in a list view display within SmartInfo pop-up section that has a close box. GAGNP 3/10/08

Parent class

Through directed inheritance, the immediate parent class of the Rule-HTML-Section class is the Rule-Obj-HTML class.

Preview and Run

After you save this rule form, click the Preview toolbar button () or type the equivalent keyboard shortcut CTRL+ALT+P to see a more faithful split-screen presentation of the runtime appearance of the section. (Many sections depend on context. Even when the section is correctly configured, the Preview display may fail and report JSP errors if this section rule depends on clipboard contents that do not exist or other rules that cannot be found.) BUG-7472 rejected

Click the Run toolbar button () to test the section with data from the clipboard. See How to test a section rule.

As with the Layout tab, the system renders both the Preview and Run displays using the styles of the skin rule identified in the Skins field of the Run Process In group of your General preferences. If the Skins field is blank, these displays use the styles marked Work on the Styles tab of the skin identified in your current portal rule. See Designer Studio — Setting your preferences. 5.5 GRP-503

Security

If your application RuleSets contain section rules that are not auto-generated, run the Rule Security Analyzer before locking a RuleSet Version, to look for possible security issues.

	fragment, harness, SmartInfo, stream processing
	About Harness rules JavaServer Pages tags Understanding CSS styles Example: Embedded list view display in a flow action
	Atlas — Standard section rules

About Section rules