List view Question and Design multiple version of SOR (System of Record) pattern ?
1. What is the pattern used when a customer has to work with mutiple version of SOR (System of Record) ? The SOR does not change dramatically and most changes are database records (like rates, pricing and threshold) and not the structure of DB itself. Currently customer uses list views to pick the different version of SOR (DB instance) in following way
Class DB mapping (Class1 and Clas2 are child of Class)
Class maps to DB
Class1 maps to DB1
Class2 maps to DB2
They used list view under Class to pick the correct version of Database based on ClassName. So when they passed Class1 in “listView” as ViewClass parameter they got results from DB1 version. Now they cannot do this since moving to Pega 7.
2. Has the behavioiur of listview changed ?
The behavior in list view( which is deprecated) seems to have changed in version 7.1.9 Now it is picking the version based on “Applies-To-Class” rather than the DB-table Class mapping as described above). So in 719 even if one executes list view by
Passing “Class2” as View class parameters they are getting the results from DB instead of DB2 since this is where ListView “Applies-To-Class” is based.
There is an open SR-A95708 for this issue but thought I will put this here anyway.
***Updated by Moderator: Lochan. Removed user added #helpme tag. Apologies for confusion, shouldn't have been an end-user option; added Category and SR Exists tag***