I’m currently going through Data Pages in Pega and wanted to check if I understood the difference between Copy data from a Data Page and Refer to a Data Page correctly.
My understanding is that Refer to a Data Page is better when the case should always show the latest data from the source system. On the other hand, Copy data from a Data Page makes more sense when the case needs to keep the data as it was at a specific point in time.
For example, if a case should always show the customer’s current contact details, I would use Refer to a Data Page . But if an order needs to keep the price from the moment the order was placed, I would use Copy data from a Data Page .
I also read that when using a savable Data Page , copying the data is recommended to avoid accidental overwrites.
Does this sound right? Are there any common mistakes or best practices I should keep in mind when deciding between these two options?
Use Refer to a Data Page when the case should point to the source data rather than own a separate copy of it. This suits data that can change outside the case and should be read as current, subject to the Data Page’s refresh strategy. e.g.: current customer contact details, office information, product/reference information, current account balance, or live availability.
Use Copy data from a Data Page when the case needs to retain a point-in-time snapshot. The values are copied into the case property when initially populated, so later changes in the source system do not automatically change the case’s stored business record. e.g: Order price at order submission, quoted terms, address used for delivery, eligibility result at assessment time, or the version of a policy applied to a case are typical examples.
The key decision is therefore not just “current versus historical,” but also:
Who owns the data? the case or the external/SOR ?
Is the data read-only, or will the case update it?
@recep.demir Yes, your understanding looks correct. Refer to a Data Page when the case should always use the latest data from a shared source. For example, a currency conversion application may reference an Exchange Rate Data Page so calculations always use the current exchange rate from the external system. If the rate changes, the case automatically sees the updated value.
Copy data from a Data Page when the case needs to preserve data in its historical context. For example, when an order is submitted, you would copy the product price, tax rate, or exchange rate into the case so the transaction reflects the values that were in effect at that point in time. Even if those values change later, the case retains the original snapshot for auditability and business consistency.
A simple rule of thumb is: Refer = live/shared data, Copy = historical snapshot or case-owned data. For savable Data Pages, copying is often preferred to avoid unintended updates to the system of record and to keep case data independent from source data.