Links may not function; however, this content may be relevant to outdated versions of the product.
Use control rules to determine the appearance of a single property, such as a button or drop-down field, on a form.
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.
- Standard controls
As you build forms, use standard controls to bring consistency and predictability to the look and feel of your application. Use the Records Explorer to see a complete list of the standard controls available to you.
- Advanced Controls
- Creating a custom control
If no predefined control meets the needs of your application, you can create one.
- Controls form Completing the Controls tab
Pega Platform includes a set of standard auto-generated controls. As a best practice, use these controls to save development time and ensure consistency. By default, this tab is displayed when you open an auto-generated control or open a New rule.
- List View form - Understanding the HTML tab
HTML tab on the List View form
- Declare Trigger form - Completing the Pages & Classes tab
Use this tab to list the clipboard pages referenced by name in the Triggers tab. See How to Complete a Pages & Classes tab for basic instructions.
- Control form - Actions tab
Action sets determine the behavior of a control.
- More about Controls
- Viewing generated Java code of Access When rules
- About Navigation rules
Use a Navigation rule to construct a multi-level XML document to be used in navigation and context menus.
A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.
Previous topic Harness and Section forms - Configuring an External web component section Next topic Standard controls