Skip to main content


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

Adding single-value fields to forms

Updated on November 22, 2021

Collect specific, single pieces of information from users when they process a case by adding a single-value field to a form. For example, you can add a field that references a phone number to a form that prompts users to enter their personal and address details.

  1. Navigate to a place where you want to add a single-value field:
    ChoicesActions
    Add a single-value field to a case type in App Studio
    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 box, click Add field.
    Add a single-value field to a case type in Dev Studio
    1. In the navigation pane of Dev 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 box, click Add field.
    Add a single-value field to a data object in App Studio
    1. In the navigation pane of App Studio, click Data.
    2. Click Data objects and integrations.
    3. Click the data object that you want to open.
    4. On the Data model tab, click Add field.
    Add a single-value field to a data type in Dev Studio
    1. In the navigation pane of Dev Studio, click Data types.
    2. Click the data type that you want to open.
    3. On the Data model tab, click Add field.
  2. In the dialog box, in the Field name field, enter a unique name for the field.
  3. In the Type list, define a field type:
    ChoicesActions
    Add a text paragraph to the form
    1. In the Type list, select Text (paragraph).
    2. Click the Configure paragraph icon.
    3. In the dialog window, in the Display as list, define whether to display the paragraph as plain or rich text.
    4. Click Submit.
    Add a picklist to the form
    1. In the Type list, select picklist.
    2. Click the configure options icon.
    3. In the dialog window, in the Display as list, define a display mode for the picklist.
    4. In the Picklist options, define choices for the picklist.
      You can create your own choices or source them from a data view.
    5. Click Submit.
    Add an attachment field to the form
    1. In the Type list, select Attachment.
    2. Click the Choose the attachment category icon.
    3. In dialog window, in the Attachment category list, select the category.
    4. Click Submit.
    Add a user reference to the form
    1. In the Type list, select User reference.
    2. Click the Configure user reference icon.
    3. In the dialog window, in the Select record using list, define whether users can search for a user ID by using a search box or a drop-down list.
    4. Click Submit.
    Add a location field to the form
    1. In the Type list, select Location.
    2. Click Submit.
  4. If you are adding fields to a case type in App Studio or Dev Studio, in the Options list, define a display mode for the field:
    • 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).
  5. Click Submit.
What to do next: After you add a new field, the field becomes part of a data model for your case type, so that you can reuse the field in other forms. For more information, see Reusing fields on forms.

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