Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Applying design templates

Updated on April 5, 2022

Make your applications consistent and save development time by using design templates. Design templates represent common user interface patterns and specify regions in which you add user interface elements, such as icons and controls.

For example, a Card with image template provides a space for a large image at the top of the user interface and a space for fields and controls below.

  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 new a case by clicking Save and run.

  3. In the open case, hover over the view that you want to edit, and then click Configure this view.

  4. In the configuration pane on the right, click the Change template icon.

  5. In the Select a template window, click the template that you want to apply to the view.

  6. In the configuration pane on the right, add fields, sections, and controls to the template:

    1. In the header of the area to which you want to add the UI component, click the Add icon.

    2. In the Add list, hover over the component that you want to add, such as a text field, and then click the Add icon.

  7. Optional:

    To remove a component from the template, hover over the component name, and then click More optionsDelete.

  8. Save the configuration by closing the configuration pane.

  • Controls

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

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