Advanced options for a harness
You can define how your application generates 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 a harness rule, you can customize HTML to meet the needs of your application.
Advanced options
The following table lists the settings that govern HTML creation in a harness rule:HTML settings in a harness
| Setting | 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 selecting. Client-side validation detects and marks invalid input earlier, and it 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 isin the fragment rule WorkFormStandard. |
| Enable expression calculation | Causes the application to 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 a portlet-compliant harness form to an external portal server through Service Portlet rules and display it in a portlet window. A harness is portlet-compliant only when its sections are also portlet-compliant. The Work-.SimpleConfirm standard harness is an example of a portlet-compliant form. |
| Localize | Indicates that the application can localize the text in this harness. At run time, if your application contains a translated ruleset for a user locale, the harness displays the text in the relevant language. This check box is available only when
you set Generate For to
|
| Do not display dirty warnings | Prevents the harness from displaying warnings about unsaved work. |
| Create skeleton | Generates a placeholder UI when the application loads the harness. |
| 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 UI displays the Do not display in channel content list check box. |
| Document type | Overrides the document type for the harness. By default, the application rule determines the document type. You can select one of the following document settings:
|
| IE document mode | Determines how the harness uses document compatibility mode in Microsoft Internet Explorer. You can select one of the following document settings:
|
| Enable client-side template UI | Sets the template-based rendering of the UI. You can select one
of the following settings:
|
| ID | Sets an alphanumeric ID for this layout for use in JavaScript
functions. The system attaches the ID attribute to the
|
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.
Previous topic Harness form - Presenting flow actions Next topic Sections