Skip to main content

Data sources

Use the Data sources section of the Data Page form to specify how Pega Platform™  populates the contents of a Data Page when an application references the page. To configure a data source, specify the type of the source and the name of the data source. You can use any of the following options to configure a data source for a Data Page:

  • Data Transform
  • Activity
  • Connector
  • Report definition
  • Database lookup
  • Robotic Automation
  • Robotic desktop Automation
  • Aggregate sources
  • Lookup

For each source type, you identify the data source to query.

The following example shows a data source configured to populate a Data Page with a list structure by running the DataTableEditorReport for the class GoGo-GoGoRoad-Data-Customer:

Data page uses Report definition as its Source

You must configure a Data Transform to map the response to the Data Model for the Case Type or Data Type when:

  • Using a report definition to source a page structure
  • Using a lookup to source a list structure
  • Using a robotic Automation
  • Using a robotic desktop Automation

Data sourcing from multiple data sources

If you must combine data from multiple sources to populate a Data Page, select the Aggregate sources option. Then, identify each of the data sources to query. Pega Platform populates the Data Page from the specified sources in the listed order.

Conditional data sourcing from a data source

A Data Page must specify at least one data source. If a Data Page contains more than one source, configure a logical Condition for each source to test whether to query the data source. The Condition for the last listed data source is set to Otherwise to ensure that Pega Platform always identifies the data source for the Data Page. When an application references the Data Page, Pega Platform evaluates each Condition in the data source order and uses the data source for the first Condition that returns a result of true.

Parameters

When populating a Data Page, you may need to limit the contents of the page to relevant items. For example, a database contains records of all the policies underwritten by an insurance company. If a customer wants to adjust the coverage on their auto insurance policy, you need a way to populate a Data Page with only the relevant policy record.

You can use parameters to limit the contents of a Data Page. For example, if you select Lookup as the data source, you must provide the key value to uniquely identify the record to return to the Data Page. You can also use parameters to pass data to a report filter to limit results to a specific set of records, such as a specific product type in an inventory database. You can pass a parameter to a Data Page from user interface elements such as a drop-down or radio button, properties, and certain other Rule Types.

Note: For a full list of the Rule Types that can pass parameters to a Data Page, see Passing Parameters to Data Pages from non-UI Rules.
Caution: Using parameterized Data Pages can lead to multiple instances of a Data Page on the Clipboard. Consider the impact of these multiple Data Page instances when adding a parameter to a Data Page. If you do not need an instance for each unique combination of parameters, select the Limit to a single Data Page check box on the Load Management tab to maintain a single instance of the parameterized page that Pega Platform overwrites when the parameters change.

To use a parameterized data source, add an entry for the parameter on the Parameters tab of the Data Page record.

To reference a parameterized Data Page, include the name and value of each parameter in the reference. Use brackets to identify the name and value of each parameter, using the syntax DataPageName[Parameter1_Name:Parameter1_Value,Parameter2_Name:Parameter2_Value,...].

Note: When you attempt to access a parameterized Data Page, Pega Platform ignores any instance of the Data Page with a different value for the same parameter.

In the following Data Page image, click the + icons to learn more about parameter configurations:

Data Page references

You use a Query Field Type when data needs to be referenced from a Data Page. While most data objects created from the Integration Designer do not have a key or the other needed Data Pages to create a reference relationship, Query fields require either a list or lookup Data Page.

A Query field does not store any key values within itself, so any parameters to the Data Page are external to the field. Consider a Case Type that manages flight instruction and creates flight plans for students. The Case Type uses a query to obtain the weather for an airport by passing an airport code sourced outside of the Case. It then returns the weather details and automatically populates them on the flight plan confirmation View. 

Note: A Query field does not require the parameter to be a field sourced outside the Case, and it can have the parameter come from any field in the context of a containing object or a field from an activity. 

The Data Page or View defines parameters for a Query field. For example, a Data Page might use a date range as a parameter to determine which transactions should be returned. You can configure a Query field to copy the information from the Data Page into the Case on first access. Additionally, you can use a savable Data Page to push the information back to the system of record, such as when you update a value. 

Check your knowledge with the following interaction:


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

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 Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice