@Yasvanth Tanuku

• Node-level Data Page (Scope = Node)

  • What it is: A shared cache for the entire server node.
  • When it loads: On first reference after the node starts (or when explicitly reloaded).
  • Lifetime: Until server restart or until cache is invalidated/expired by refresh settings.
  • Use case: Reference data common to everyone (e.g., country list, exchange rates, configuration).

• Keyed Data Page (Parameterized data page)

  • What it is: A data page defined with parameters (keys). Each unique key combination creates its own cached instance.
  • Scope: Can be Node, Requestor, or Thread—keyed is about parameterization, not the scope itself.
  • When it loads: On first reference with a specific key; subsequent references with the same key reuse the cache.

• Node-level Data Page: One shared cache per node, loaded once, reused by all requestors.
• Keyed Data Page: Parameterized; one cache per unique key. Scope can be Node/Requestor/Thread—choose based on sharing and sensitivity.

@Yasvanth Tanuku Node Data Page: 1. Node data page is like , that data page is called when ever the first operator of that  access group which you define in the data page, is logged in, the data page gets initialized and stored in clipboard. 2. for the next time, if other operator want's to access the data from same data page, instead of hitting the server again, pega automatically dets the data from clipboard. 3. the node data page will automatically be flushed whenever node restarts, or the refresh strategies that you implement Keyed Data page: 1. Keyed data page is like accessing the contents of the data page by passing a key. 3. Simply keyed assess data page is like getting information from pre-loaded list of records 2. when you configure keyed data page, and when you call it any where, pega gets all the results and store in pxResults in the clipboard 3. To access any page in that page list Data page, you need to pass the index so that pega matches the index from the pxResults and gives you.

4.To access the keyed data page, you need to configure  at the property level. i,e, create the page list property and select copy data from a data page and pass the "id" as the key at the property level EX: D_OperatorDetails.pxResults pxResults(1)            pxResults(2)             pxResults(3) id: Proprietary information hidden     id: Proprietary information hidden       id: Proprietary information hidden Name: abc               Name: def                 Name: ghr Gender: Male          Gender: Female        Gender: Female So, when you initialize the D_OeratorDetails , data page and configure "id" as the key, pega stores all the results  as shown above and store in the clipboard. * in run time, when you use the property, pega gets the key value from the clipboard and access that data page by using that key. in the above example, Consider key is "id" and value is Proprietary information hidden in the run time, if you use the property and want to retrieve the gender and name the result will be: Gender: Female Name: def