Table of Contents

Advanced options for a harness


Only available versions of this content are shown in the dropdown

You can define how your application generates the HTML code to save processing power and improve the user experience. Each time you save a harness, Pega Platform generates source HTML. By understanding the advanced settings in the harness rule, you can customize HTML to meet the needs of your application.

Advanced options

The following table presents the rules that govern HTML creation in a harness rule.
Field Description
Enable client side validation

Causes the application to validate the input that the user enters in a field even before the user submits the entire form.

You can use this feature in applications where users enter data, such as text or dates, by typing rather than selection. Client-side validation can detect and mark invalid input earlier, and generates less network traffic.

Standard client-side validation scripts are in the webwb.CSValid.js text file rule. For localization purposes, the corresponding error messages are in the CSValid HTML fragment rule . You can add custom client-side validation scripts or error messages on an application-wide level by overriding the UserWorkFormHTML fragment rule , which is included in the fragment rule WorkFormStandard.

Enable expression calculation

Allows the application to automatically recalculate the target properties of a declare expression rule and properties that are involved in constraints rules.

The system updates the display when the user focus leaves the input field for a property. For more information, see More about Declare Expression rules.

Portlet compliant

Generates portlet-compliant HTML that a portal server can display. Portlet-compliant HTML meets the requirements of Java Specification Request 168, which defines the portlet standard.

You can send portlet-compliant harness form 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 is an example of a portlet-compliant form.


Indicates that the application can localize the text in this harness. If your application contains a translated ruleset for a user's locale, at run time, the harness displays the text in the relevant language.

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

For more information, see Localizing your application.
Do not display dirty warnings

Prevents the harness from displaying warnings about unsaved work.

Create skeleton

Generates a placeholder UI when the harness loads.

Work area

Designates the harness as an area where documents open for processing in the application.

If you select the Work area check box, the Do not display in channel content list appears.

Document type

Overrides the document type for the harness. By default, the document type is inherited from the application rule.

You can select one of the following document settings:

Inherit from application rule
Uses the document type set on the application rule. The default for new applications is HTML 5.
HTML 5 (standards mode)
Always renders in standards mode
None (quirks mode)
Always renders in quirks mode.
IE document mode

Determines how the harness uses document compatibility mode in Internet Explorer (IE). You can select one of the following document settings:

Pega default
No compatibility mode. The browser does not emulate older versions of IE.
The same as the default. No compatibility mode and the browser does not emulate IE.
Provides you with tools to set the X-UA-Compatible Mode on the harness to ensure that the application can emulate a specific version of IE.
Enable client-side template UI Sets the template-based rendering of the UI. You can select one of the following settings:
Pega default
Does not use template-based UI.
Turns on template-based UI, which runs on desktop, mobile, and in offline mode.
The same as the default. Does not use template-based UI.
ID Sets an alphanumeric ID for this layout for use in JavaScript functions.

The system attaches the ID attribute to the <body> HTML element of the harness.

HTML Source

Displays a read-only version of the harness in HTML.

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

Have a question? Get answers now.

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