Harness, Section, and Flow Action forms
Adding a section

Field

Description

On different object

Click the checkbox if you want to add a section rule using a page other than the current section rule.

Applies To

By default, the the Applies To key part of the current section appears in this field. If you wish, you can select a a child or ancestor class.

Purpose

Select the Purpose key part of the section rule.

Using page

This field appears when you select the On different object checkbox. Identify the name of the page that is the basis for fields (properties) within this section. If the page is in the same class as the current rule, the system updates the Pages & Classes tab when you save the rule. If you name a page in a different class, the name must be defined on the tab before saving the rule.

Of class

This field appears when you select the On different object checkbox. By default, the Applies To key of the current section appears. If you wish, select a different Applies To key. The class name must be defined on the Pages & Classes tab of the current section rule before you save the rule.

Purpose

This field appears when you select the On different object checkbox. Select the Purpose key part of the section rule.

Field

Description

Use Section

Select or confirm the Purpose key part of the section rule. Click the pencil icon () to open or create the section rule. Click the magnifying glass icon ( ) to enter parameters for the section or to share the current parameter page with the section. The Applies To key is, by default, the same as the current section. pashm v6.1

Refresh When

Optional. Enter a simple Java expression evaluated upon JavaScript events as part of a client event to cause this section to refresh from the server when the expression evaluates to true. GRP-229

For example, enter .Color =="Blue" in this field to make this section refresh when the property Color changes to the text value Blue. See Implementing dynamic form actions and the Client Event Editor. C-1990

Field

Description

Optional. Enter a positive number for the width in pixels of this cell. (At runtime, normal browser processing for rendering tables determines the actual displayed width.)

This field appears only when the Unit field in the Layout panel or Repeat panel (for the layout containing this cell) is set to px fixed. You can also adjust the width of columns directly:

1. Click a vertical wireframe cell border.
2. Wait until the pointer shape changes (), then drag the border. PROJ-281

Optional. Enter a positive number for the height in pixels of this cell. (At runtime, normal browser processing for rendering tables determines the actual displayed height.)

This field appears only when the Unit field in the Layout panel or Repeat panel (for the layout containing this cell) is set to px fixed. You can also adjust the height of a row directly:

1. Click a horizontal wireframe cell border.
2. Wait until the pointer shape changes (), then drag the border. PROJ-281

Select Always or Other Condition. Choose Other Condition to make the visibility depend on a when condition rule, a Boolean expression evaluated only once, or a test evaluated repeatedly upon JavaScript events.

If you selected Other Condition for the Visible field, complete this field. Enter an expression involving other properties, or identify the When Name key part of a when condition rule. PROJ-283 Specify one of three outcomes:

• When condition rule — Enter the When Name key part of a when condition rule that determines the visibility of this field at runtime. The system uses the Applies To key part of the current rule in rule resolution to locate the when condition rule. Click the pencil icon () to review or create the when condition rule.
• Expression evaluated once — Enter an expression that returns true or false. This expression can involve multiple properties, function calls, and other syntax as supported by the <pega:when > JSP tag.
• Simple Java expression evaluated upon JavaScript events — To dynamically control the visibility of this property with a JavaScript event, enter a simple comparison involving target properties and select the Run on Client? box. The result at runtime determines whether the content of this cell appears in read-only mode or in the mode of the enclosing layout.
  For example, enter .Color =="Red" in this field to make this section visible when the property Color has the value Red, and invisible otherwise. Depending on the state of the Run on Client checkbox, the comparison can be executed only once as the form is initially displayed, or dynamically. You can use parentheses and the || and && operators to group and combine multiple single-property comparisons. See Implementing dynamic form actions and the Client Event Editor. C-1990

This field appears only if you select Other Condition for the Visible field and a simple expression in the When field.

Select to indicate that the When field contains a simple property comparison test that will be evaluated on the user workstation in response to a client event. See Implementing dynamic form actions and the Client Event Editor.

Clear to indicate that the When field contains a when condition rule name or an expression to be evaluated once upon initial display of the form.

Select to cause the section to be presented in read-only styles, even when the form is in read-write mode, always or conditionally.

Optional. Enter an expression involving another property, or identify the When Name key part of a when condition rule. PROJ-283 Specify one of three outcomes: REMOVED RUN ON CLIENT per KUCHS 3/7/07

• Leave blank to present the content in read-only mode always, regardless of the mode of the enclosing layout.
• When condition rule — Enter the When Name key part of a when condition rule that determines the mode of this field at runtime. The system uses the Applies To key part of the current rule in rule resolution to locate the when condition rule, and executes the When rule once as it renders the form. Click the pencil icon () to review or create the when condition rule.
• Expression evaluated once — Enter an expression that returns true or false. This expression can involve multiple properties, function calls, and other syntax as supported by the <pega:when > JSP tag.

This field appears only when you select the Read Only checkbox.

Field

Description

Optional. By default, when the work object form or flow action form appears in read-write mode, the CSS style named DataValueWrite applies. You can enter another style name or select from those listed.

Click the pencil icon () to review the text file rule that defines the style sheet. Your application can override the standard style sheet.

Optional. By default, when the work object form or flow action form appears in read-only mode, the CSS style named DataValueRead applies. You can enter another style name or select from those listed.

Click the pencil icon () to review the text file rule that defines the style sheet. Your application can override the standard style sheet.

To apply inline styling to this cell only, type a CSS style definition in this field, or click the magnifying glass to access a Style Editor window. Styles you enter in this field supplement and override style elements defined in style sheets, according to standard CSS rules.

Inline styles are recorded in the generated HTML for the form; they do not alter the CSS definitions.

Using the Style Editor

You can select the font, color, font size, text align, vertical align PROJ 242 – TASK 16156, borders, margins, and other attributes of this cell using selection lists. The Style Editor maintains a preview of the resulting presentation. If you alter the style definition directly, click  Apply   to update the preview.

Click OK   to record the style defined with the Style Editor in the panel.

Field

Description

You can review or change the section you identified earlier.

Choose a format to control what appears above the layout (known as a header or subheader), and the appearance of both the header and any subheader, and aspects of the body.

This choice primarily affects styles and appearance. Information in or below a subheader (including Hidden Sub) presents information that is right-indented from information in a header.

Using the Branding wizard, you can review or revise the styles (colors, fonts, padding and margins) associated with each header or subheader format.

Enter text to appear in the header or subheader. This text may include directives or JSP tags, such as <p:r > or <pega:lookup >.

If you plan to localize the application using this rule so the application can support users in various languages or locales, choose the text carefully and limit the length to no more than 64 characters. When practical, choose a caption already included in a language pack, to simplify later localization. A field value rule with this text as the final key part is needed for each locale. See About the Localization wizard.

This field is not visible if the Format field contains No Format, Hidden, or Hidden (Sub).

This field appears if the Format field contains Custom. Identify the Stream Name (second key part) of an HTML rule that defines the content of the header.

Optional. To control visibility of the section, enter or select one of the following:

• Leave blank to present the section always.
• A when condition rule. SR-7276 B-25698 BUG-1665 gone? Click the pencil icon () to review or create the when condition rule.
• Expression evaluated once — Enter an expression that returns true or false. This expression can involve multiple properties, function calls, and other syntax as supported by the <pega:when > JSP tag.
• Simple Java expression evaluated upon JavaScript events — To dynamically control the visibility of the body with a JavaScript event, enter a simple comparison involving a target property and select the Run on Client? box. The result at runtime determines whether the content of this cell appears in read-only styles or in the styles of the enclosing layout.
  For example, enter .Color =="Red" in this field to make section body visible when the property Color has the value Red, and hidden otherwise. Depending on the state of the Run on Client? checkbox, the expression can be executed only once as the form is initially displayed, or dynamically. See Implementing dynamic form actions and the Client Event Editor. C-1990

Optional. To force refresh of this section at runtime based on a test, enter a simple Java expression evaluated upon JavaScript events involving a property comparison or multiple property comparisons using the || and && operators and parentheses. Click the pencil icon () to review or create the property rule.

Field

Description

Optional. To control the conditions under which the section controls are active, enter the following:

• Leave blank so that the section is always active.
• A when condition rule. SR-7276 B-25698 BUG-1665 gone? Click the pencil icon () to review or create the when condition rule.
• Expression evaluated once — Enter an expression that returns true or false. This expression can involve multiple properties, function calls, and other syntax as supported by the <pega:when > JSP tag.
• Simple Java expression evaluated upon JavaScript events — To dynamically control the visibility of the body with a JavaScript event, enter a simple comparison involving a target property and select the Run on Client? box. The result at runtime determines whether the content of this cell appears in read-only styles or in the styles of the enclosing layout.
  For example, enter .Color =="Red" in this field to make section body visible when the property Color has the value Red, and hidden otherwise. Depending on the state of the Run on Client? checkbox, the expression can be executed only once as the form is initially displayed, or dynamically. See Implementing dynamic form actions and the Client Event Editor. C-1990

Optional. To control visibility of the body of the section, enter or select one of the following:

• Leave blank to present the body always.
• A when condition rule. Click the pencil icon () to review or create the when condition rule.
• Expression evaluated once — Enter an expression that returns true or false. This expression can involve multiple properties, function calls, and other syntax as supported by the <pega:when > JSP tag.
• Simple Java expression evaluated upon JavaScript events — To dynamically control the visibility of the body with a JavaScript event, enter a simple comparison involving a target property. The result at runtime determines whether the content of this cell appears in read-only styles or in the styles of the enclosing layout.
  For example, enter .Color =="Red" in this field to make the body visible when the property Color has the value Red, and read-write styles otherwise. Depending on the state of the Run on Client? checkbox, the comparison can be executed only once as the form is initially displayed, or dynamically. See Implementing dynamic form actions and the Client Event Editor.

Identify the name of the page that is the basis for fields (properties) within this section. Leave this field blank if the page is the one matching the Applies To key part of the rule.

Optional. To restrict the presentation of this section (in read-only mode) to those users who hold a specific privilege, select a privilege name. Click the pencil icon () to review or create the privilege rule.

Optional. To restrict the presentation of this section (in read-write mode) to those users who hold a specific privilege, select a privilege name. Click the pencil icon () to review or create the privilege rule.

If a user holds the privilege in the View Privilege field but does not hold the privilege identified in this field, the section appears in read-only format. In this case, default values for fields are not shown. B-14313 rejected MARTT 4/7/06