Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Harness form - Completing the Advanced tab

Updated on April 5, 2022

Harness form - Completing the Advanced tab

Each time you save a harness, Pega Platform generates source HTML from your entries on the other tabs of this form. Complete the fields on this tab to control how the HTML is generated.

> Advanced Options

Enable Client Side Validation Select to cause Pega Platform to immediately validate the format of user input to dates, integers, and other fields within the browser window when focus leaves the form field, before a user submits the form.

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.

Enable Expression Calculation

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.

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.

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 rule type Service Portlet is deprecated. Use Pega Web Mashup instead.

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

Localize Select to indicate that at runtime, presentation of this harness will be localized based on field value rules in a language-specific ruleset.

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:

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.

Document type The Document type determines the rendering of the application user interface. The document type is set on the Application rule.

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.

IE document mode Select one of the following to determine how document compatibility mode in Internet Explorer is utilized:
  • 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.
Enable client-side template UI Select one of the following to use the template-based UI for rendering the harness".
  • 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.
ID Optional. Enter an alphanumeric ID for this layout for use in JavaScript functions.

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

> HTML Source (Read Only)

Select the expand icon to view a read-only display of the generated HTML. You can review, but not directly alter, the HTML text on this tab.

At runtime, Pega Platform uses stream processing to evaluate the JSP tags and this source HTML (which references properties and other rules such as HTML fragment rules, HTML rules, controls, and sections) in the context of the current clipboard contents and static files.

Pega Platform then returns the resulting HTML to the browser on the client workstation.


  • Keystores

    A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

  • JavaServer Pages tags
  • Stream processing of JSP tags

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us