Skip to main content

Controls

Suggest edit Updated on December 13, 2021
Applicable to Theme UI-Kit applications

Use control rules to determine the appearance of a single property, such as a button or drop-down field, on a form.

Note:

Your user privileges determine which properties you can configure for controls. If you have access to Dev Studio, then you can access the full property panel in App Studio. If you do not have access to Dev Studio, then you have access to the simplified property panel.

  • Data capture controls

    Data capture controls help you gather information from the application users in a more intuitive way. You can use a variety of preconfigured controls that correspond to different types of data in the application. For example, the Currency control captures monetary data and formats it accordingly.

  • Picker controls

    Picker controls present the user with a number of options from which to choose the value of a field. For example, the Dropdown control displays a list of possible choices in an expandable drop-down box.

  • Action controls

    Action controls provide your users with tools that launch operations or change the state of the application. For example, you can use the Link control to add active links to the case form.

  • Data display controls

    Data display controls help you represent data graphically in the form of maps, charts, or images. For example, the Timeline control creates a display of events that occur over a period of time plotted against the date.

  • About Navigation rules

    Use a Navigation rule to construct a multi-level XML document to be used in navigation and context menus.

  • Creating a custom control

    If no predefined control meets the needs of your application, you can create one.

  • Styling a control

    Customize an application to match the branding requirements of your business by changing the look of the user interface. You can modify an application at run time by styling individual controls, such as buttons or text fields.

  • Defining the behavior of form elements

    Ensure that users see and complete only the fields that are relevant to the processing of a case by defining the rules that govern the behavior of form elements.

  • Adding text to form elements

    Ensure that users fill in the forms in an application correctly by supplying brief instructions. Provide additional information for users through labels, helper text, and placeholders that appear on form elements.

  • Adding actions to a control

    You can specify action sets—event-action pairings—to determine the behavior of a control. For example, you might specify that clicking a button triggers the refresh of a section. You can define multiple events and actions in an action set, and you can create multiple action sets for a single control.

  • Selecting the property reference for a control

    Select a property for the control to determine the data type to include in the list that an application user sees. At run time, the user selects one or more values from the list.

  • Automating source synchronization in controls

    Improve the maintainability of your application by defining sources for the values that populate user interface controls. When you tie a control to a list source, the values in the control change automatically to reflect the state of the source, which saves development time.

  • Specifying presentation options for a control

    After you create a control, you configure how the control is displayed. You can specify whether the control is editable at run time, the width of the control, the label format for the control, and one or more CSS helper classes to adjust the control's appearance and placement.

  • More about Controls
  • Previous topic Harness and Section forms - Configuring an External web component section
  • Next topic Data capture controls
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us