Keyed data pages

Keyed data pages are used to avoid querying the database every time a user interacts with the application. Instead, they cache the information within the case, so whenever the data is accessed, it is already preloaded on the case clipboard. This makes the application more efficient and reduces database hits.

When to use keyed data pages  

In my experience, the most common use of keyed data pages is for dropdowns and sometimes tables. The Pega CSSA course provides examples of when to use this type of data page. From my perspective, keyed data pages are ideal when you need to filter data. You send the parameters for the data, and the keyed data page returns a filtered list based on those parameters. 

Sometimes i encountered scenarios where you need to query data form an external database, and making queries every time that we change a parameter can affect the preformance to the application, this could impact directly on the user making the interface slow and could lag sometimes, to avoid this whe use a key data page

How to configure a keyed data pages 

1. Create a data page 
2. on the structure we select List
3. on the mode of the data page we select Read-Only 
4. Scope we select Thread
5. On the Keyed page access cheked the option Access pages with user defined keys
6. On the Page list keys , we select the .pyGUID as the default identificator

Important notice:

A keyed data page can only be read-only and the structure must be a list, you cannot use keyed data pages for savable or editable page mode