Skip to main content


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

Reusing fields on forms

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

Save time and build forms that are convenient to maintain by referencing fields on other, existing forms. For example, you can reuse a field group to capture different user details on a new form, such as name, surname, mailing address and phone number, instead of creating separate fields for each item.

  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. On the Workflow tab, click Life cycle.
  3. In the Case life cycle section, click an assignment or an approval step.
  4. In the Step properties panel, click Configure view.
  5. In the dialog window, click Fields.
  6. Click Add to view next to the field that you want to reuse.
  7. Optional: To change the default display mode of the field, in the Options list, select a new mode:
    Note: You cannot change the display mode of a field when its value is calculated by using an expression.
    • To indicate that users can optionally complete the field, select Optional.
    • To indicate that users need to provide the value in the field, select Required.
    • To indicate that users can only view the field, select Read-only.
    • To indicate that users can only view the field and an application determines the value at run time, select Calculated (read-only).
    You configure the default display mode when you first create a field. For more information, see Adding single-value fields to forms.
  8. Click Submit.
  • Restrictions on field and form reuse

    You can reference an existing field or form when you build a new form. By reusing components in your application, you save time and avoid duplication.

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