Complete this tab to define the HTML and JSP tags or directives for this rule.
|Omit extra spaces?|
Typically, the system sets this field to
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.
|Browser Support||Indicates which browser types can display the JSP or HTML from this rule. Note that the Pega Platform does not validate your code. You must ensure that your code can be displayed across the supported browser types, which include Internet Explorer 7+, Firefox 3.5+, Safari 4+, and Chrome 5+.|
to indicate that you have designed and implemented your HTML to meet your accessibility requirements.
The Accessibility Report evaluates this field on each rule in an application that displays it, when calculating application accessibility compliance levels. See Using the Accessibility report.
Enter source HTML directly in the
text area. .
Use of JSP tags in HTML rules offers superior performance and other advantages over directives. Although both directives and JSP tags are supported, as a best practice use JSP tags in new application development. Conversion of existing HTML rules that use directives to functionally equivalent rules that use JSP tags is straightforward. See Converting from directives to JavaServer Pages tags.
When using JSP tags, update the Pages & Classes tab to include each page name referenced in the HTML code, and identify the class of each page.
Use the <% and %> delimiters to surround an inline Java scriptlet within the HTML source code.
|Convert to JSP||
This button appears only after you save the form when the
|Show JS DOC||Reserved; do not use.|
Notes on <Form > and <Input > HTML tags
Stream processing automatically supplies attributes for the following HTML tags:
FORMtag, the system supplies all needed attributes. Enter this tag with no attributes.
If you omit the
NAMEattribute with directives for the
TEXTAREAtags, and the
INPUTtag (with a
Checkbox), stream processing fills in the name of the current active property.
INPUTtags, if you do specify a
NAMEattribute, stream processing may alter it to ensure that is processes correctly when a user submits the form at runtime.
INPUTtags in JSP streams, the
NAMEfield is required. The format is:
<INPUT name=""<pega:reference name=""$this-name""/>""
- Introducing JavaServer Page tags
- Stream processing of JSP tags
- About HTML rules
Use an HTML rule to describe how the system is to assemble, through stream processing, portions of HTML displays in your application.
- HTML rules -
As a best practice, before creating a new HTML rule, it is strongly recommended that you investigate using an auto-generated section instead. The New form displays a message with information about that alternative.
- More about HTML rules
Referencing other rules and static files