Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adding custom attributes for version 1 DX API to auto-generated controls

Updated on February 7, 2022

Improve the flexibility of application development and increase control over UI components by adding custom attributes for version 1 Pega Digital Experience (DX) API to auto-generated controls, such as buttons or text input controls.

The attributes that you add are part of the DX API response. The front-end solution in which the controls are used interprets the attributes to run a corresponding activity. For example, you can add an attribute that generates a tooltip text for a specific field.
  1. In the navigation pane of Dev Studio, click Records.

  2. Expand the User Interface category, and then click Section.

  3. In the list of sections, locate and open the section with the controls to which you want to add attributes.

  4. If the section is based on a template or created in App Studio, at the top of that section, click Convert to full section editor.

  5. In the section, click the control that you want to modify, and then click the View properties icon.

  6. In the Cell Properties dialog box, expand the Identifiers category.

  7. In the DX API Attributes section, add your custom attributes:

    Note: The attributes are specific to your custom UI. You can retrieve the list of attributes by using a REST call.
    1. Click the Add attribute link.

    2. In the Name field, enter a meaningful label for the attribute.

    3. In the Value field, enter the value of the attribute.

    For example: To add a tooltip to a control that captures the user's last name, in the Name field, enter tooltip, and then, in the Value field, enter Enter last name.
  8. Click Submit.

  9. On the rule form, click Save.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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