Skip to main content

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

Rule types used

Updated on August 27, 2020

The application data objects are implemented through data set rules. Data sets represent a data object and can be logical, physical, or both.

The data set and the data set properties are defined by the class to which the data set applies to. The data set can also define the physical location of data such as relational database table, a NoSQL object, or even the application clipboard. Data sets are highly flexible. At run time, the application accesses the data sets to retrieve the data needed for AI and marketing purposes.

For more information about data sets, see About Data Set rules.

Data sets can be loaded and retrieved through data flow rules. Data flows manage the movement of data from source to destination within Pega. Data flows can also transform your data. This is the primary mechanism used to "flatten" data in Pega Customer Decision Hub for Financial Services.

For more information about data flows, see Processing data with data flows.

Data flows rely on report definition rules, such as LoadCustomerSummary, to query data from your systems. Use report definitions to identify the columns and filters in your data model against which you want to pull. Customers create their own report definitions for their data models.

For more information about creating a report definition rule, see Report Definition rule form.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us