This feature can affect input of dates, times, text areas, and selected other properties, in sections of the user form other than the Take Action section. This feature depends on the control associated with the property. See client-side format validation.

Select when users are to enter dates, times, integers, or text through typing rather than through selection. Workstation-level validation can detect and mark invalid input earlier, and may consume less network traffic and bandwidth. Do not select if the user form presented by this harness contains only check boxes, selection lists, combo boxes, and other input widgets that do not require typing.

Standard client-side validation scripts are in the text file rule named webwb.CSValid.js; to allow for localization, the corresponding error messages are in the HTML fragment rule named CSValid. You can add custom client-side validation scripts or error messages on an application-wide by overriding the HTML fragment rule named UserWorkForm, which is included in the fragment WorkFormStandard, which in turn is included in the HTML code for every user form.

Select to enable automatic recomputation and redisplay of all target properties of a Declare Expression rules that appear on the user form, and automatic evaluation of constraints rules associated with properties on this form, immediately after the user touches an input field. This feature is sometimes known as "calculated values".

You can select this check box if the user form defined by this rule:

• Displays one or more properties computed by Declare Expressions rules using forward chaining, or one or more properties involved in constraints rules
• Allows users to input a property value that affects the computed property (directly through forward chaining) or the constraints

Computation occurs (and the system updates the display) as user focus leaves the input field for a property. See Viewing generated Java code of Access When rules.

For example, the form may contain a total that sums values entered into an array.

A portlet-compliant harness form can be sent to an external portal server through Service Portlet rules and displayed in a portlet window. A harness is considered portlet-compliant only when its sections are also portlet-compliant.

The standard harness Work-.SimpleConfirm provides an example of portlet-compliant form.

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. See:

• Internationalization and localization
• Localization wizard
• Localizing forms and reports with the Field Value Inspector

This check box is available only when Generate For is set to JSP.

When Localize? is 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.

You can override the Document type for the selected harness, if desired. If you do not want to override the Document type set in the application, accept the default, Inherit from application rule.

Select one of the following to determine rendering of this harness:

• Inherit from application rule : this harness renders using the Document type set on the Application rule.
• HTML 5 (standards mode) : this harness renders in standards mode, regardless of the Document type set in the Application rule.

• None (quirks mode) : this harness renders quirks mode, regardless of the Document type set in the Application rule.

HTML5 document type is the default for new applications.

• PRPC default : no compatibility mode. The browser will not emulate older versions of IE.
• None : the same as default. No compatibility mode is set, so the browser will not emulate anything.
• Other : allows you to set the X-UA-Compatible Mode on this harness to ensure that a specific version of IE can be emulated and overrides the compatibility view setting.

• PRPC default : The template-based UI is not used.
• Yes : Turn on the template-based UI. When selected the template-based UI runs on desktop, mobile web, Pega Mobile Client, and offline.
• No : The same as default. The template-based UI is not used.

The ID attribute is applied to the <body> HTML element in the harness, for easier reference in custom scripts and styles.