Node Level Data pages in Constellation
Hi Team ,
Why Node Level data pages wont work in constellation applications ?
Publicis Sapient
IN
Hi @Adithya_A,
In Constellation, node-level data pages aren't supported because Constellation is built to show data that’s specific to each user or case. Since node-level pages are shared across all users, they don’t fit this model.
Updated: 17 Jun 2025 2:43 EDT
Rulesstack Private Limited
IN
Hi @Adithya_A,
In Pega Constellation applications, Node-level data pages are not supported primarily due to architectural and design principles that focus on cloud-native, scalable, and stateless deployments. Here’s a breakdown of why they don’t work:
1. Constellation Is Built for Stateless Environments
Constellation applications are designed to work in stateless environments like Pega Cloud, Kubernetes, or containerized deployments. In such environments:
-
Application nodes can be added or removed at any time.
-
Node-level memory or caches are not shared between nodes.
-
A node-level data page created on one node is not accessible on another.
This breaks consistency, which is unacceptable for cloud-native applications.
2. Single Page App (SPA) Architecture
Constellation uses a React-based frontend and DX APIs for communication. Each API call must be:
-
Stateless
-
Predictable
-
Able to run independently on any node
Node-level data pages, which store data in memory on a specific node, contradict this design. Thanks & Regards,
Ajay Kumar.
Updated: 18 Jun 2025 7:57 EDT
UNUM Group
US
@Ajay Kumar Atmakur : Wondering how requestor & thread level data pages is working in stateless constellation architecture, I believe thread level & requestor level data pages work in same way in the server side as there will not be any thread created for each case in Single Page UI. So basically everything is at the requestor level ?
Pegasystems Inc.
PL
@Adithya_Aeach request towards the server is separate DX API call. Each DX API call create new thread and it removed when processing is finished. Ultimately there is no difference between thread and requestor data pages in context of life span.
UNUM Group
US
@Kamil Janeczek will the DX API call (/data_views) fail if we use Node level Data Pages ?
Pegasystems Inc.
PL
@Adithya_Adid test it, my guess is it will not fail. Anyhow it will be quick test. Please share the observations.
UNUM Group
US
@Kamil Janeczek Yes ,i tried that and it was working , i was able to use a node level data page in the authoring view as well and it worked (meaning no error) , but i was not able to check the difference between thread/requestor/node level pages how it is behaving differently
UNUM Group
US
@Kamil Janeczek : How is the server side data page cache maintained for Thread Level vs Requestor Level data pages (List) ?
ex: say there are below 2 read only data pages , if we open 2 cases will there be 2 cache created for each case for thread level data page ?
1. D_SampleThreadLevelList
2.D_SampleRequestorLevelList
HCA Healthcare
US
Node-level data pages do not work because Constellation uses a modern design that runs mostly on the browser (client side) and connects to the server using APIs. Node-level pages are shared across users on the server, but in Constellation, each user’s data must stay separate for security and performance. Since Constellation is stateless and doesn’t keep data on the server for long, it doesn’t support shared memory like Node-level pages. This helps the app run faster and scale better across users. If you need to use data pages, it’s better to use Thread-level or Requestor-level data pages which work well in this setup. These types of pages only store data for one user at a time, which fits the Constellation model
UNUM Group
US
@Sairohith Based on my test , Node Level data pages are working in 24.2.1 , below is my test run
created a list view which used Node Level Data Page List (non parameterized) to display table row , this data pages used a data transform to fetch a value from application settings rules ex: say "data123" , now i logged with user 1 and open a case to see "data123" in the table row , after that i updated the value in app settings rule to "data456" and logged with other user 2 and i could still see "data123" in table row , even i tried logging off user 1 as well , even i created a new case still i could see old value which id due to node level data page cache , so untill i did clear cache from data page via dev studio i was not able to see the updated value .