Skip to main content


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

Adding action buttons to a case header

Updated on December 13, 2022
Applicable to Hybrid mode applications

Create shortcuts to frequently performed actions in a case, by adding more action buttons to a case header.

To be consistent with the design, present the action buttons added to the case header as icons.
Before you begin: Ensure that your application is upgraded with the Cosmos Design System to customize a portal in the phone preview.
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. In the work area, run a case by clicking Save and run.
  3. Complete the Create dialog box, and then click Create.
  4. On the case page, enter the design mode by clicking Design in the upper-right corner.
  5. Hover over the case header, and then click the Edit this section icon.
  6. In the properties pane on the right, in the Additional actions section, click the Add icon.
  7. In the ControlsActionsButton menu, click the Add to view icon.
    Result: The new button appears in the case header and in the Additional actions section of the property pane on the right.
  8. In the case header, hover over the new button, and then click the Edit this field icon.
  9. On the General tab, in the Text field, delete the text.
  10. From the Image source drop-down list, select Icon Class.
  11. Select an icon for your new button by clicking the Search icon next to the Class field.
  12. On the Presentation tab, from the Control format drop-down list, select Other.
  13. In the Other control format field, enter, and then select Icon.
  14. On the Actions tab, add a required action to the new button.
    For more information about adding actions, see Adding action sets to a control.
  15. Click Apply.

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