Complex data class structures
Hi all,
I need to créate a complex data class structure where there will be a few data classess nested or embedded. For instance, something like:
Provider.Building(1).Company(1).BusinessLine(1).Product(1).SubProduct(1).Service(1).Tariff.Price
I wonder whether there is any nice way to define a complex data class structure in a way that i should not make use of so many embedded pages/page list.
I have read about reference properties but i do not want to use them as we have several issues to work with it in the past.
My concern about creating the above data class structure is that we will have to create a few declare index in order to browse providers based on Building data class properties, Company data class properties or any propety belonging to any embedded page list.
I think there´s no other way to do it but i would like know whether there is any alternative way to set this up in order to make the data class structure more simple without so many nested page list.
Any help would be very much appreciated.
Regards,
Israel
Pegasystems Inc.
FR
Hello Israel,
I think Reference Properties is surely an option for that kind of scenario. What sort of issues were you having using them?
What Pega version are you running?
Iris Global Soluciones
ES
Hi Marc,
I am using Pega 7.4 but will be upgraded to Pega Infinity in a month.
I am concerned about using reference properties in case i need to define declare expressions or any other pega rule on them and i could come accross with some limitation due to being a reference property. Do you know any limitations, restrictions or constraints when using reference properties?
In the past we also had some issues with reference propety to delete them when no longer needed.
Regards,
Israel
Areteans
AU
HI @IsraelU1,
The key is ,
1. You basically need to sit aside and understand the business,
2. then you need to identofy the possible data model which needs to be created as Customer, LoanDetails, EmployerDetails, IncomeDetails, ReferenceDetails etc
3. Then you need ti think through and understand how all these data model can be related to each other..
ex., Is 'referenceDetails' part of 'Customer' ?Can One customer have multiple Reference details..?If yes then you should probably relate these 2 Data model as One to Many Customer - To -ReferenceDetails.
In the end no data model is perfect, It's on you how you think through and create one as per your application.
Thank You.
Iris Global Soluciones
ES
Hi SiddhantJivane,
Thanks for the quick response.
We have gone through all the points you talk about. We have identified the entities involved and their relationships but we want to implement the data model with the correct structure. Pros and Cons of using page lists or page groups for the above example? Should we use a reference property to make the above example more readable and maintenable and for not duplicating data in Clipboard? We must also take into account how to create or manage reports whether our data structure is mainly built in Page List or Page groups.
Regards,
Israel