Show all
A section rule can appear within another section, panels and containers within a harness
rule, or within a layout cell. (You cannot edit a section that is
within a cell directly; open the section rule.)
Sections define reusable rectangular sub-areas of a harness, section,
or flow action. For example, the standard section
Work-.CoreSummary is included in both the
Work-.New and Work-.Perform harness rules. This
achieves modularity, ensures a uniform appearance, and reduces the number
of rules you need to maintain and update when you later need to revise
work object forms.
Before you save a Harness, Section,
or Flow Action form, review and adjust the layout. If a section is
expanded when you save the form, it appears initially expanded at
runtime; if a section is collapsed when you save the form, it appears
initially collapsed at runtime.
You can embed sections within
sections within sections. The maximum recommended depth is four levels.
CLINIC 7/11/06
Drag and drop
the Section controlupdated v6.1 pashm
If the section is in a layout cell, complete the fields and tabs of the
Cell Properties panel. If the panel is pinned (
), the wireframe presentation
on the rule form changes immediately to reflect of your inputs. If the
panel is not pinned (
), click Apply to apply your inputs. GRP-229
Top fields
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
|
General tab
Field
|
Description
|
Width
|
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:
- Click a vertical wireframe cell border.
- Wait until the pointer shape changes (
), then drag the border. PROJ-281
|
Height
|
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:
- Click a horizontal wireframe cell border.
- Wait until the pointer shape changes (
), then drag the border. PROJ-281
|
Visible
|
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.
|
When
|
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
|
Run on
Client
|
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.
|
Read Only
|
Select to cause the section to be presented in read-only
styles, even when the form is in read-write mode, always or
conditionally.
|
When
|
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.
|
Advanced tab
Field
|
Description
|
Read-Write
Style
|
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.
|
Read-Only
Style
|
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.
|
Inline Style
|
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.
|