Skip to main content

Data Pages in Constellation

In Pega Platform™'s Traditional UI architecture, Data Page processing is run completely on the server side, while in the Constellation architecture Data Page processing can also be handled on the client side.

Data Pages and the DX API

DX APIs are stateless, which means that after a request is fulfilled, the session (requestor) that processed the request is closed. This means that:

  • Any thread/requestor-level Data Pages that are created to fulfill the request are not available for the next request from the same browser session.
  • With the Constellation architecture, Data Pages are able to be cached on the client side to further improve application performance.
  • So as not to lose all caching benefits that Data Pages provide, a cache is maintained on the server.
Note: With the DX API, Data Pages are also referred to as Data Views.

Data Page server-side cache

With Constellation, a cache of Data Pages is kept on the server, but because of the stateless architecture there needs to be a way to link a browser session to the thread/requestor-level Data Pages created from that session. 

The cache is maintained using the psync_id element, which is passed in the payload of the Pega-AAT cookie, as seen in the following figure:

Example of a Pega-AAT cookied with the psync_id element.
Note: Pega-AAT is a JWT token. AAT stand for Authorized Access Token and is generated by Pega's OAuth2.0/authorize endpoint.

The cache is maintained either in the JVM memory or in the database.

Read-only Data Pages are cached server-side with the exceptions, as follows:

  • Thread and Requestor scope read-only pages are cached, except when:
    • Reload one per interaction is selected
    • Keyed page access is enabled
    • The Data Page is searchable or queryable
    • Clear pages after non-use is selected
  • Editable Data Pages do not get cached
  • Single-page Data pages do not get cached

Client-side caching

In the Constellation architecture, Data Pages are also eligible to be cached on the client side to provide further performance benefits. 

You can check the contents of the client-side cache using the function PCore.getDataPageUtils(). You can run this function in the browser's DevTools Console.

Note: For relevant training materials about the PCore API and browser DevTools, see Tools for debugging Constellation applications. For more information about how Data Pages function in Constellation, see Data Pages in Constellation.

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