Question
Stratosphere Technical Consulting
US
Last activity: 14 May 2020 14:58 EDT
Data Page in activity - data consistence design
A parameterized data page is of node scope and reload every hour. An activity has 10 steps with each step's step page is the parameterized data page with same parameters. In each step, the system will check if the data page is fresh and reloaded if needed (as shown in Tracer). Though it is rare but possible that during processing this activity, the data page is expired in the middle. As such, the step 1 and step 10's data page content will be different.
What is the recommended design pattern if I need to maintain consistent data page content within the different steps of the activity? Is this something I sure even worry about?
Thanks
Updated: 12 May 2020 21:30 EDT
Pegasystems Inc.
US
Hi,
If your design insists to keep this as a node-level data page rather than requestor scope, I think maybe there is an extremely rare possibility of new data page getting loaded in activity steps. Can you consider copying the parametrized data page to a temporary page at step1 that can be used as a step page to maintain consistency and later remove it after activity execution?
Let me know your views!
Stratosphere Technical Consulting
US
Node vs Thread is always such a delicate balance. Thread has better data consistence but less re-use of contents between threads.
Regarding copying data to thread, that is what I think as well. Thanks for confirming.