Control form
|
|
Optional. Identify parameters for this control. This tab appears only if the rule is non-auto-generated as specified by the Auto-Generated? check box on the HTML tab.
Parameters are supported on controls identified in flow action, section, and harnesses. (Parameters are allowed only for JSP-based rules.)
Use of parameterized controls — both standard rules and those you build for your applications — is recommended for flexibility and to reduce the number of distinct controls in your application.
For a partial list of standard rules that accept parameters, see Standard Controls with parameters.
This tab is wide. To display more of the content, click the collapse arrow (
) in the portal to temporarily hide the navigation panel. When you finish working with this tab, click the expand arrow (
) to display the navigation panel again.
Field |
Description |
| Name |
Use the following syntax to identify complex parameters:
As with scalar parameters, these complex parameters are not true properties — no Rule-Obj-Property rule exists for them — but they mimic the structure of the property types. Complex parameter definitions are accepted on this Parameters tab, on the Parameters tab of the Section form. Use the <pega:param > JSP tag, within the <pega:reference ..> JSP tag, to set values for complex and scalar parameters. Typically, complex parameter values are used within the scope of a <pega:foreach ..> JSP tag. |
| Description |
Optional. Enter descriptive text to document the purpose of each parameter. This description appears when a developer completes parameter values. |
| Data Type |
Select |
| Required? |
Select to indicate that the parameter (of data type Leave cleared for Boolean parameters. |
| Type for SmartPrompt |
Optional. To aid application developers in selecting a value for this parameter, identify a concrete class that has a single key part, such as Data-Admin-Operator-ID. This instructs the system to let developers complete this parameter value through a SmartPrompt selection rather than by typing; it has no runtime effect. |
|
Validate As |
Optional. Identify a |
| HTML Fragment for Parameter Prompting |
Optional. Identify an HTML fragment rule that can prompt developers (when completing the Format form) with descriptive text for each parameter. |