Section form
|
Adv Parameters reference a flow action, or gadget, within a section.
Parameterized sections provide flexibility and promote reuse. For example, a single section may include a button which has one of three labels — Increase, Decrease, and Clear — depending on the value of a section parameter. (Since that button always calls a single activity, some mechanism within that activity must operate at runtime to determine the context and desired result.)
Using parameterized section rules can promote reuse and reduce the
number of distinct section rules you need in your application. Be careful
to ensure that each parameter has a value in each enclosing rule
(section, harness, or flow action) that includes the section.
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 |
Parameters Type |
Select a class value for this parameter, identify a concrete class that begins with PegaGadget-. Classes must inherit from PegaGadget in Adv Parameters. This instructs the system to let developers complete this parameter value through a SmartPrompt selection rather than by typing; it has no runtime effect. Or, Click to Create a New Class. |
Parameters Display |
Select the flow action applied to the class referenced above. This flow action needs to contain a section applied to your class, where you define how to enter data for your parameters. The flow action can also reference a Rule-Obj-Validate rule to run validation on the entered data. Or, Click to Create a New Flow Action. |
Default Values |
The Default Values button opens up your flow action/section so you can enter default values for your parameters. |