Atlas — Standard controls accepting parameters |
Your system contains hundreds of standard controls (formerly HTML Property rules). Use the Records Explorer to see a complete list of the standard and custom controls available to you. Standard controls described in the table below accept input parameters.
As a best practice when feasible, use these parameter-based or auto-generated controls to present properties in the fields of sections, flow actions, and harnesses rather than controls that do not accept parameters. Your application uses fewer distinct rules and operates more efficiently. In hand-edited HTML code, use the <pega:param > option of the <pega:reference > JSP tag to supply parameter values. See Standard controls without parameters and Standard auto-generated controls.
PRPC 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. tools.putParamValue("DateFormat","2");
tools.getParameterPage().remove("DateFormat).
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 user form and is:
Several of the standard rules listed in the following table accept three optional parameters named ReadOnlySmartInfo, ReadWriteSmartInfo
and SmartInfoHeader
:
ReadOnlySmartInfo
parameter value.ReadWriteSmartInfo
parameter value.SmartInfoHeader
parameter.You can leave either or both parameter blank, or identify the same section 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 Harnesses, Sections, and Flow Actions — Adding an Autocomplete control. |
||||||||||||||||
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. |
||||||||||||||||
Date |
Presents a localizable date in one of several formats depending on parameters. Accepts six input parameters: For new development use pxDateTime. |
||||||||||||||||
DateTime |
Presents 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. 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:
|
MenuBar | Supports menus within composite portals. See Harnesses — Adding a menu bar control. |
MultiSelectList |
Allows a user to select one or more items from a short list. For an example, see the standard section 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 %. Set 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. |
RadioButtons |
Similar to PromptSelect, but presents the values as a group of radio buttons determined by one of the following:
Complete two parameter values to control the appearance of the radio buttons:
For example, given a property with the Table Type field specified as the 24 text values Alpha, Beta, Gamma through Omega, and you select Using field value rules, your application can localize button labels at runtime. |
RichTextEditor |
For a text value, allows the user to enter HTML markup such as <b> and <i>, and JSP tags. For example, the email text in the Body field of the standard flow action Work-.SendEmailCorr allows users to include such markup in outgoing emails. As a best practice for security reasons, use the standard edit input rule pyFilterRichText to process user input into such fields. See Property form — Completing the Advanced tab. |
reporting_image |
Allows a clickable image to appear in a list view 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. |
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. 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 and Section forms — Adding a SmartLabel control. |
SplitButton |
Presents a button but allows access to a drop-down list of alternatives. See Split button. |
Text |
Presents an HTML text box with a specified display size and a maximum input length, both in characters. Set values for three parameters:
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 |
Presents 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 Code-Pega-List.OrgChart. |
WorkArea |
Supports display of user forms in a composite portal. See Harnesses and Sections — About the Work Area control. For new development, use a dynamic container. See Harness and Section forms — Adding a dynamic container. |
Standard controls 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(...)