Skip to main content


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

Using data pages in forms

Updated on April 6, 2022

Use data pages to present information to end users on forms. Data pages make it easy to access and load data on demand.

By using data pages in your forms, you only need the application data model to understand the data. Data pages contain all the details needed for calling the integration from the form, which saves you time on development.

The following are the most common use cases for using data pages in forms. To illustrate these use cases, consider an example of a job recruiter who is running a job applicant case.

  • Use a data page to display information in a collect information step in a case. You configure a collect information step to display a form and gather information from a user.

    For example, a recruiter is preparing to interview a candidate for the Senior Software Engineer position at a local tech company. The recruiter searches through a list of jobs on the form in order to find the details of the Senior Software Engineer position. The list of jobs is populated by a data page.

    For more information, see Collecting information from a user.

  • Use a data page to show the details of the option that the user chooses from a list.

    For example, the recruiter finds the Senior Software Engineer position in the list and selects it. The form then displays the details of the job by using a data page.

  • Use a data page to update data and persist the changes as part of a case.

    For example, a recruiter is running a case to update the details of a job posting. The case presents the recruiter with a form that displays the job details in text input fields, such as Description and Responsibilities. The recruiter updates the appropriate fields and resolves the case.

    By updating the fields on the form, the recruiter updated the data page that contains the job details. When the recruiter resolves the case, the system persists the updates to the location in which the job is posted.

    Another example involves a hiring manager who notifies the recruiter that the job is filled. The recruiter then marks the job as filled on the form. As a result, the data page that contains the job posting details is updated, and the updates are persisted through the case. When the case advances to the resolved step, the case persists the changes that the recruiter made to the remote system of record to update the job status to fulfilled.

    For more information, see Updating connections and field mappings for a data object.

  • Previous topic Passing parameters to data pages from autopopulated properties
  • Next topic Identifying data pages with the Live Data tool

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