Question
Accenture
NL
Last activity: 10 Feb 2020 12:53 EST
How to extend a data class to higher layers
How to extend a data class to higher layers
Enterprise-level data classes can be referenced by Enterprise level Work- classes. Similarly, implementation-level data classes are normally referenced by implementation level Work- classes. Enterprise-level <Org>-Data- classes should also be able to be referenced by implementation level <Org>-<App>-Work cases. So how can an enterprise-level data class (i.e.: <Org>-Data-Warranty) be referenced by an implementation level <Org>-<App>-Work cases? Or how can an enterprise level Work- case reference an implementation level data class? The solution is to use Dynamic Class Referencing (DCR).
What do they mean by referencing here?
So how can an enterprise-level data class (i.e.: <Org>-Data-Warranty) be referenced by an implementation level <Org>-<App>-Work cases? - Do they mean creating a Page property in the work class and use the enterprise level data class as the definition for the page? If yes then it is possible to create it right?
Doesn't the below two statements contradict each other?
Enterprise-level <Org>-Data- classes should also be able to be referenced by implementation level <Org>-<App>-Work cases.
So how can an enterprise-level data class (i.e.: <Org>-Data-Warranty) be referenced by an implementation level <Org>-<App>-Work cases?
How to extend a data class to higher layers
Enterprise-level data classes can be referenced by Enterprise level Work- classes. Similarly, implementation-level data classes are normally referenced by implementation level Work- classes. Enterprise-level <Org>-Data- classes should also be able to be referenced by implementation level <Org>-<App>-Work cases. So how can an enterprise-level data class (i.e.: <Org>-Data-Warranty) be referenced by an implementation level <Org>-<App>-Work cases? Or how can an enterprise level Work- case reference an implementation level data class? The solution is to use Dynamic Class Referencing (DCR).
What do they mean by referencing here?
So how can an enterprise-level data class (i.e.: <Org>-Data-Warranty) be referenced by an implementation level <Org>-<App>-Work cases? - Do they mean creating a Page property in the work class and use the enterprise level data class as the definition for the page? If yes then it is possible to create it right?
Doesn't the below two statements contradict each other?
Enterprise-level <Org>-Data- classes should also be able to be referenced by implementation level <Org>-<App>-Work cases.
So how can an enterprise-level data class (i.e.: <Org>-Data-Warranty) be referenced by an implementation level <Org>-<App>-Work cases?
Please help me understand this one.
Aaseya IT Services Pvt.Ltd
IL
Hi Dinesh,
To extend any class to higher levels either we can do it using built on application(in which our implementation is built on the Framework which inherits enterprise level classes) or defining the enterprise class as Parent Class in the Class Definition of your Implementation class. Both ways can help you to inherit the enterprise classes.
Thanks,
Satish Mogilicherla.