Posted: 24 Oct 2019 13:59 EDT Last activity: 30 Oct 2019 8:22 EDT
Extending data types for implementations
I have multiple implementations off a common framework. I have a data type and each implementation has its own records. I could add a column to the data type that represents a unique value for each implementation to separate the records by implementation. Is there a better way to do this? Can I use inheritance to extend the data type for each implementation without having to change the code using this data type in my application? Perhaps this data type is used for a dropdown on my UI for example. What does Pega suggest for this? If I extend the data type to my implementation I obviously need to create a new data type. Then I suppose override the data pages and report defs or perhaps I can utilize the feature of a report def to return records from desendant classes instead.
***Edited by Moderator Marissa to update platform capability tags****
I think having additional column like imp application name or any other flag is good design and you can use this as parameter in datapage or reportdefination for reusability. We have followed same approach in past .