Atlas — Standard control rules accepting parameters |
Your system contains more than 600 standard control rules (formerly HTML Property rules). Use the Rules by Type Explorer to see a complete list of the standard and custom control rules available to you. Standard control rules described in the table below accept input parameters.
VERY LONG TOPIC -- HOW TO SPLIT UP ?
As a best practice when feasible, use these parameter-based or auto-generated control rules to present properties in the fields of section rules, flow actions, and harness rules rather than control rules that do not accept parameters. Your application uses fewer distinct rules and operates more efficiently. C-2281C-2413 In hand-edited HTML code, use the <pega:param > option of the <pega:reference > JSP tag to supply parameter values. PRKB-20657 See Standard control rules without parameters and Standard auto-generated control rules.
Process Commander offers three places you can specify values for these parameters:
Single Value
properties). Click the
Configure button to the
right of the Control field to enter
parameter values for all presentations of the property.
PROJ-64
tools.putParamValue("DateFormat","2");
tools.getParameterPage().remove("DateFormat).
The Calculated Value parameter
Several of the standard rules listed in the following table accept
a Boolean parameter named CalculatedValue
. Set the
CalculatedValue
parameter to true when the property
appears in a work object form and is:
Several of the standard rules listed in the following table accept
three optional parameters named ReadOnlySmartInfo,
ReadWriteSmartInfo
and SmartInfoHeader
:
PROJ-1019 5.4
ReadOnlySmartInfo
parameter
value.ReadWriteSmartInfo
parameter
value.SmartInfoHeader
parameter.You can leave either or both parameter blank, or identify the same section rule for both cases.
Purpose |
Description |
||||||||||||||||
AutoComplete |
Presents a dynamically assembled list of text-matched candidates, constructed by an activity or from an existing clipboard page. For details and parameters, see Harness, Section, and Flow Action rules — Adding an Autocomplete control. 5.4 PROJ-890 |
||||||||||||||||
CurrencyAmount |
Formats a number as currency using the default locale.
Complete two parameters plus the
See Concepts — Internationalization. For new development, use the auto-generated control pxCurrency. |
||||||||||||||||
DataGrid |
Implements a flexible, powerful control to review or edit Page List or Value List properties. See Harness, Section, and Flow Action forms — Adding a DataGrid control.GRP-234 |
||||||||||||||||
Date |
C-2413Presents a localizable date in one of several formats depending on parameters. Accepts six input parameters: For new development use pxDateTime. |
||||||||||||||||
DateTime |
C-2413Presents a localizable
For new development use pxDateTime. |
||||||||||||||||
Decimal |
Formats a numeric value on output with a thousands separator and specified precision locale, for example 1,234.567. Enter up to five parameters:
|
||||||||||||||||
DynamicSelect | Supports the Dynamic Select control. PROJ-163 See Harness, Section, and Flow Action form — Adding a Dynamic Select Control. |
Purpose |
Description |
Integer |
Formats a numeric value on output with a thousands separator and specified precision and locale. Enter values for up to four parameters: KHATV 5/5/06 remove Locale
|
MenuBar | Supports menus within composite portals. See Harness rules — Adding a menu bar control. GRP-237 |
MultiSelectList |
Allows a user to select one or more items from a short list. For an example, see the standard section rule PegaAccel-Task-CircumstanceSearch. FindByCircumstance_Circumstances. |
Percentage |
Formats a numeric value on output as a percentage value, for example the value 0.043 can be presented as 4.31 %. C-2413Set three parameters: For new development, use the auto-generated control rule pxPercentage. |
PickState |
Presents a list of two-character state codes for the
states of the United States. Set the |
PromptSelect |
On input, presents a drop-down selection list of values
determined by the Table Type area of the
General tab of a property rule.
The Table Type field can specify a
This allows users to select from a familiar or easy-to-understand list of values, while a hidden value corresponding to a user selection becomes the property value. If the Set the Entries on the list can be localized at runtime through field value rules. |
pzLPEllipsis |
When specified as a control rule for a text field or a field in a display, truncates the displayed text and adds an ellipsis ("...") when the text exceeds a stated width. The full value appears in the tooltip for the field. The property takes as a parameter the maximum width of the field in pixels.v 6.1 |
RadioButtons |
Similar to PromptSelect, but presents the values
determined by the Table Type area of the
General tab of a property rule as a group of radio buttons. The
choices for Table Type are
Complete two parameter values to control the appearance of the radio buttons:
For example, if the Table Type's fields
specify the 24 text values Alpha, Beta, Gamma through
Omega, and you select Using field value rules, your application can localize button labels can be localized at runtime. |
reporting_image |
Allows a clickable image to appear in report cell. Create and reference in parameters an activity that executes upon click. Parameters are:
|
reporting_link |
Allows a clickable link to appear in a report cell. Create and reference in parameters an activity that executes upon click. Parameters are:
|
Purpose |
Description |
SearchPanel |
Supports multi-criteria search. NO EXAMPLES 5.5 |
SmartInfo |
Used with read-only property values. Presents a pop-up window displaying a read-only section when the user hovers the mouse pointer over the field value. The user can click the window or press any key to close the window. The window contents can explain the significance of the selected value or provide other guidance. For example, if the read-only value is a state code such as CA for California, text in the pop-up window can explain how California regulations affect what the user can enter in other fields. C-2563 5.2 Complete three parameters:
By design, the pop-up window does not appear when the mouse pointer hovers over a blank value. The pop-up is for display, not user input. Don't identify a section that contains input (read-write) fields. |
SmartLabel |
Allows you to present a pop-up window when a user clicks on a specially styled label, normally presented in red font. Parameters for the SmartLabel rule are the same as for the SmartInfo rule. See Harness, Section, and Flow Action forms — Adding a SmartLabel control. PROJ-1019 5.4 |
SplitButton |
Presents a button but allows access to a drop-down list of alternatives. See Split button. GRP-223 |
Text |
DeprecatedPresents an HTML text box with a specified display size and a maximum input length, both in characters. Set values for three parameters: SR-9297 BUG-3020
Processing other than input processing is
unaffected by the Spell checking is enabled by default. For new development, use the auto-generated control rule pxTextInput. |
TextArea |
DeprecatedPresents an HTML <INPUT TYPE="textarea"
...> with specified size and expansion. Set the
For new development, use the auto-generated control rule pxTextArea. |
Time |
Present a
|
TreeGrid | Supports an interactive tree structure display. For an example, review the standard section rule Code-Pega-List.OrgChart. |
WorkArea |
Supports display of work object forms in a composite portal. See Harness and Section rules — Adding a Work Area control. GRP-264 |
R-10388 Standard control rules with names ending in
i18n
(such as Date-Long-i18n) accept a
parameter for the locale. For these rules, you can't supply
parameters through the Formats form or the Parameters tab. You can set a parameter value with the
PublicAPI call:
tools.putParamValue(...)