Section form - Completing the HTML tab
Each time that you save an auto-generated section, Pega Platform derives source HTML from your entries on the Design tab.
Select in most cases to allow
to generate HTML text for the section based on information in the
Hand-edited HTML in sections can introduce complex, difficult-to-debug processing into your application. Clear this check box only when necessary. Following the guardrails, avoid hand-edited HTML in sections when other approaches can achieve the same result. As a best practice, use the Rule Security Analyzer to detect and correct for security vulnerabilities.
If this rule is later saved with the Auto-Generated HTML box selected, your HTML changes are overwritten.
|Portlet compliant|| Select to generate portlet-compliant HTML that can be displayed by a portal
server. Portlet-compliant HTML meets the requirements of Java Specification Request
168, which defines the portlet standard.
This box is available only when the Auto-Generated HTML box is selected.
A portlet-compliant section form can be sent to an external portal server through Service Portlet rules and displayed in a portlet window.
The rule type Service Portlet is deprecated. Use Pega Web Mashup instead.
Select to indicate that at runtime, user presentation of this section is to be localized based on field value rules in a language-specific ruleset text elements.
This check box is available only when
is selected and
is set to
For each locale, you must add field value rules in such a ruleset to support presentation of this section. Typically, use the Localization wizard and the Rules Inspector tool to identify, create, and maintain these field value rules.
When selected, the generated HTML calls the PublicAPI Java function getLocalizedTextForString() at runtime to convert text in the pyCaption, pyButtonLabel, pyActionLabel, pyActionPrompt and other properties to a locale-specific value.
|Omit extra spaces|
Enter your code using HTML, CSS, JS, Flash, Flex, and so on in the HTML Source area.
When you select this option, the
tab displays an array for entering the names and descriptions of
Typically, the system sets this field to
Use of JSP tags in sections offers superior performance and other advantages over directives. Although both directives and JSP tags are supported, JSP tags are recommended for new development.
If the Auto-generated HTML box is not selected, use only JSP tags or directives — not both — in the custom HTML you add to this rule. Set this field to reflect your choice.
This field indicates which browsers and versions can correctly process the HTML code from this rule.
option is selected, the value is
option is not selected, and you edit the generated code or manually provide the code for the rule, select
This field is available when
is not selected.
The Accessibility Report evaluates this field on each rule in an application that displays it, when calculating application accessibility compliance levels. For more information, see Using the Accessibility report.
uses stream processing to evaluate the JSP tags or directives in this source HTML (which reference properties and other rules such as HTML fragment rules, HTML rules, controls and sections) in the context of current clipboard contents and static files.
then sends the resulting HTML to the HTTP server, which transmits it and the associated static files (images, scripts, and style sheets) to the Internet Explorer browser on the client workstation.
To edit the generated source:
Sections are the building blocks of your user interface. You can populate a section with components, such as fields and controls, to create a functional chunk of user interface that can be reused in different contexts for improved consistency and efficient development.
- Stream processing of JSP tags
- JavaServer Pages tags