Table of Contents

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.

The following restrictions apply when reusing a field or form:

  • You cannot change the field type.

  • You cannot change the class of a field group or repeating field group.

  • You cannot change the data type that is associated with a data reference.

  • You cannot reuse single-value fields that are defined in a repeating field group or field group.

If you change the name of a field after you reuse it on a form, your application creates a new field with the new name.

  • Reusing fields on forms

    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.

  • Reusing forms

    You can reduce development time and maintain consistent layouts between sets of fields in your case type by embedding forms in other forms. For example, you can prompt users to review their employment history by embedding their Work History form in a Confirmation form.

  • Referencing data from another data object

    Create reusable data for your application and build easy to maintain forms by using a data reference.

  • Forms and fields

    A form is a view of your data. The fields on a form store user input that can include single-value fields, a group of values, or a list of values. After you create a form, you can associate it with an assignment or approval step in the life cycle of a case.

Have a question? Get answers now.

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