Clarification on Data Object Sourcing
Can someone explain the reasoning behind why each data object corresponds to its respective sourcing mechanism, as shown in the attached image, based on the context provided in the question?
HCA Healthcare
US
Each data object in Pega is connected to a specific source based on where the most reliable and updated data comes from. For example, if customer details are stored in an external system, then the data object uses a REST API to fetch that information in real-time. If the data doesn’t change frequently, like a list of countries or products, it can be stored directly in Pega for faster access. This mapping helps ensure that Pega always uses the most accurate and efficient way to get data. It also improves system performance by avoiding unnecessary external calls when the data can be stored locally. The choice depends on how often the data changes, how critical it is to get the latest value, and where the system of record is.
Evonsys
NL
Thank you @Sairohith
Evonsys
NL
According to your explanation, this is what I understood with regard to the attached sample question:
Since customer or product records may change frequently or may be stored in an external system/database, their source of record is considered an external system of record.
On the other hand, since feedback consists of only three predefined constant values, it is sourced internally within the Pega application.
Is my understanding correct?
And could you please clarify why "Preference" is considered as "No system of record"?
Publicis Sapient
IN