Skip to main content

Data storage options

Common Data Model can connect to external systems of record for entity data and can also store entity data locally. You can integrate with a different storage option on an entity-by-entity basis.

There are three options available in Pega Platform™ to store entity data. You typically implement a combination of these approaches depending on the entity.

Note: In Common Data Model, by default the core entities use local storage. This configuration includes the components that integrate the data with your application, including core entities and their associated Data Pages and Data Transforms. The components use Common Data Model's design patterns and naming conventions. In many cases, a customer uses their own databases, also known as external data storage. To integrate external storage for an entity, you modify the existing Data Pages and Data Transforms.

Store data in Pega Platform (local storage)

Create and store the data in Pega Platform, as shown in the following figure. This method works directly out of the box.

local storage configuration

For the local storage option, review the following items before storing entity data:

  • The default deployment model for core CRM entities is to import data into the physical storage of Pega Platform through a set of high-quality APIs and integration gateways. To import data, you use the Pega Platform APIs or Business Intelligent Exchange (BIX).
  • Pega Platform provides local physical storage for core CRM entities. The default integration is built against this physical store.
  • Pega Platform abstracts the source of data as with any software integration, but Pega Platform always builds to a known quantity that has known scalability, performance, messages, and error handling.

Store a copy of data in Pega Platform (local copy)

You want to store data locally in Pega Platform and update other systems and databases with changes, as in the following figure:

local storage with copy

To set up this option, perform one of the following actions:

  • Create a copy of your existing system of record (SOR) data. You can bulk upload a copy of SOR data build using scheduled updates to Pega Platform from your master data management solution.
  • To extract data to your master data management solution, use the Pega Platform APIs or Business Intelligent Exchange (BIX).

Client is the System of Record (SOR) and Pega Platform is a pass-through to the SOR

You can create a connection to an external SOR and integrate the data with your application through Common Data Model, as in the following figure: 

external storage configuration

With this storage method:

  • The system does not store data in Pega Platform tables, including link tables.
  • You point Data Pages in Pega Platform to your APIs for all create, read, update, and delete (CRUD) actions. As a result, the system updates the data in your SOR. By using data pages and aggregate data sources, you can integrate your SOR and join with the data that is in Pega Platform.

This Topic is available in the following Modules:

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

Did you find this content helpful?

100% found this content useful

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