Skip to main content


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

Fields

Updated on February 7, 2022

Fields model data in your application UI and define what information you need to provide to reach your business goals.

For example, in a process of hiring new employees, you can create properties that correspond with the personal details of a candidate, such as a name, a surname, and an address.

You can adjust the type of your field to match the data that you want to collect, and pair the field automatically with a control in the UI. For example, if you want the candidate to provide an email address, you can set up a field with the type email. In the user interface, the system renders the field as an Email control. To make the development process more efficient, each field type defaults to the most intuitive control, such as a check box for a Boolean expression.

  • Adding single-value fields to forms

    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.

  • Adding data relationships to forms and data models

    To decrease application development time and costs, reuse data objects across your application by creating data relationships. When you create a data relationship, you create connections to all of the fields that you define within one data object or case type. When you update a data object, the change occurs across all of the elements that you relate to the data object. As a result, you save time and create an efficient application that is convenient to maintain.

  • Adding tables to forms

    Help users access and compare data by setting up a form with a table. Tables are a basic component that you can use to create a clear interface in information-heavy contexts.

  • 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.

  • Restricting user input in a field

    Configure fields in your data model to change the way that they store or display information to create a robust data model that is tailored to your business requirements.

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