|
![]() |
Complete this optional tab to identify HTML styles for the fields on the display, headers and footers, how user interface click events are processed, and other aspects of the presentation.
Field |
Description |
View Style | |
Style Name |
If you leave this blank, default styles apply, but vary depending on the Type field of the user's portal rule and any skin rule that the portal rule references. For additional information on styles, see:
Styles referenced here affect only the presentation of this individual list view report. You can override the styles for all list view and summary view reports at the portal level, through a skins rule that references report styles you have defined in your application. See About Skin rules. |
Field |
Description |
Row Format |
For each row, the system evaluates all the conditions (in the order you enter them) and applies the style in the first row that evaluates to true. If none is true, no style is applied. |
Evaluate Expression |
Optional. Enter the name of a when condition rule or a boolean Java expression. The when condition rule can evaluate property values in the row. For example, you can apply a special style to those rows of a list view report that contain your own Operator ID in a certain column. |
Apply this style when true |
Optional. Identify a style for a table row if the expression is true. This becomes the value of the CLASS=" " attribute for the <TR> table row element. Choose a style defined in the style sheet identified in the Style Name field. |
Optionally, you can identify styles to be applied to alternate rows of report output.
Field |
Description |
Odd Row |
|
Even Row |
|
Complete these optional fields to allow users
to select a row and operate on in using mouse clicks. The
system response can be an activity, started on the Process
Commander server, or a JavaScript function, executing in a
client Internet Explorer browser session.
If you implement this capability, make sure the Applies To class of the list view report is an external class, make sure the Key of a Row field (on the Content tab) correctly identifies a property in the external class that uniquely identifies a row.
When the parameter param.glimpseMode
is set
to the literal value "scripts
", the
system responds to click events by calling the script
identified in the call script function
field. Otherwise, it responds by calling the activity.
Field |
Description |
Events Handling | |
Single click event - call Activity |
|
call script function |
Optional. Identify a script function to run upon single click after a row is selected. |
Double-click event - call Activity |
|
call script Function |
Optional. Identify a script to run upon double-click after a row is selected. |
call script function |
(nRow, strClass, strInsName, strInsKey, strCategoryProp, strCategoryValue, lvRowItem, options) where:
Your application can call the pega.ui.LVUtils.getSelectedRows() PublicAPI function to return an array of list view rows that the user selected. |
Custom tool tip message |
Optional. Enter Tooltip text to appear for a row. |
Return properties to clients? |
|
Target Frame |
Optional. Identify the HTML frame in the display for
the output of the event. The default frame is
|
On load event call script function |
Optional. Identify a script to run when this view is first displayed. This capability is not available when the Embedded option (on the Display Fields tab) is selected. |
Fragment for script functions |
Optional. Identify an HTML Fragment rule that contains the functions identified above, or that references a static file containing the script functions.
|
Smart Info Settings (for hover)
Optionally, you can define a source for HTML code to be
rendered in a pop-up window or displayed as an embedded
<DIV> when users hold the mouse pointer over a row
(hover) or when they click a row expand arrow() at the beginning of the row. For
example, this capability can allow users to review details
about a work object on a worklist, without requiring the
users to open the work object.
Smart Info pop-ups are designed for read-only presentation. Do not attempt to include input fields or other controls.
Field |
Description |
Smart Info Settings | |
Header |
Enter text to appear in the header of the pop-up window. Alternatively, if this list view report is to be localized, identify a field value rule to contain the header text. |
Content |
Identify the name of an activity that computes the HTML text to be rendered. This activity must meet the following conditions:
For an example, review the standard activity Assign-.getWorkItemSmartInfo, which can be used to supplement worklist displays. It assembles an HTML stream by evaluating a section named Work-.WorkItemSmartInfo. (Although the standard activity is a Final rule, you can copy and override the section rule, to include fields in your application as appropriate, or copy the standard activity with a new name. The activity can return HTML code that is a partial document that contains:
Additionally, when rendered by Internet Explorer as a pop-up, the window must be modest in size.
Hold mouse pointer over any row to see details... This facility uses AJAX to communicate user requests to the Process Commander server. For an example activity that meets these criteria,
see Pega Developer Network article |
Embedded? |
Select to have the Smart Info content embedded in the report to display when you click the expand arrow at the beginning of the row. When selected, at runtime a Row Expand Arrow
( |
Field |
If blank, the Smart Info display is activated when the mouse pointer is held over any field in the row and does not move for at least 700 milliseconds. The workstation sends a request to the server to run the Content activity specified in the previous field, and the resulting HTML output appears in a pop-up window. This field appears only when the Embedded? option is not selected. |
For examples, see How to
implement "hover and see" worklists with Smart
Info and these Pega Developer Network articles:
Right-click Smart Info Settings
Optionally, you can define a source for HTML code to be rendered in a pop-up window or displayed as an embedded <DIV> when users right-click on a row. For example, this capability can allow users to review details about a work object on a worklist, without requiring the users to open the work object.
This feature works similarly to the Smart Info Settings feature, but is started at runtime by a right-click rather than by hovering the mouse pointer. Your application can provide either or both Smart Info capabilities.
Smart Info pop-ups are designed for read-only presentation. Do not attempt to include input fields or other controls.
Field |
Description |
Header |
|
Contents |
|
Field |
The workstation sends a request to the server to run the Content activity specified in the previous field, and the resulting HTML output appears in a pop-up window. |
Field | Description |
Section Settings | |
Header |
|
Footer |
|