HTML form
|
|
Complete this tab to define the HTML and JSP tags or directives for this rule.
Field |
Description |
Omit extra spaces? |
Select to eliminate extra space characters in the processed HTML. This option can make transmission or processing more efficient; it does not alter the appearance of the HTML when displayed by Internet Explorer. When selected, during stream processing the system:
Stream processing copies space characters within the text of
a property value, non-breaking spaces ( ) and space
characters within a |
Generate For |
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. B-20380 Do not save the rule form if you have composed HTML that contains both JSP tags and directives. |
Browser Support |
Indicates which browser types can to
display the JSP or HTML from this rule. Note that Process
Commander does not validate your code. You must ensure that your
code can be displayed across the supported browser types, which include Internet Explorer 6+, Firefox 3.5+, Safari 4+, and Chrome 5+. The Browser Compatibility Report in the Application Preflight tool checks this value when determining what percentage of the rules in your application provide cross-browser support. PROJ-282 5.4 |
Accessibility |
Select The Application Preflight tool evaluates this field on each rule in an application that displays it, when calculating application accessibility levels for the preflight Accessibility Report. See Using the Application Preflight tool.PROJ-901 5.4 |
HTML Source |
Enter source HTML directly in the HTML Source text area. Alternatively, click the pencil icon () to open an HTML editor. You can use JSP tags or directives in the source HTML you enter.
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. When you finish entering HTML, close the editor. Process Commander copies the HTML from a temporary file on your workstation into the HTML Source text area. 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. B-16304 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
Generate For value is |
Show JS DOC |
Reserved; do not use. Supports the Desktop API display. PROJ-116 |
VANDJ 1/21/03 Stream processing automatically supplies attributes for the following HTML tags:
FORM
tag, the system supplies all needed
attributes. Enter this tag with no attributes.NAME
attribute with directives for
the SELECT
and TEXTAREA
tags, and the
INPUT
tag (with a TYPE
attribute of
Text
, Hidden
, Password
,
Radio
, or Checkbox
), stream processing fills
in the name of the current active property.SELECT
, TEXTAREA
, and
INPUT
tags, if you do specify a NAME
attribute, stream processing may alter it to ensure that is processes
correctly when a user submits the form at runtime.INPUT
tags in JSP streams, the NAME
field is required. The format is: B-18347 ERNSG<INPUT name=""<pega:reference name=""$this-name""/>""
Some standard HTML rules used in harness and section rules contain hidden fields, defined by the HTML form element <INPUT TYPE="HIDDEN" ...>. If you override these HTML rules, do not delete or alter these hidden fields. They are essential to correct operation of work object forms.
active property, directive, open authoring, stream processing | |
About JSP tags
How to set up HTML and XML editors How stream processing works |
|
Atlas — Standard HTML rules |