Question

2
Replies
43
Views
Chakravorty Amit (AMITTUTUN)
JKTechnosoft

JKTechnosoft
SE
AMITTUTUN Member since 2011 62 posts
JKTechnosoft
Posted: November 26, 2018
Last activity: January 24, 2019
Posted: 26 Nov 2018 23:51 EST
Last activity: 24 Jan 2019 9:24 EST
Closed

Clarification regarding "Organization hierarchy specialization"

In LSA course on "Organization hierarchy specialization" it is written

"For example, some companies are so large that you can write applications specifically for one division. The code within those applications is likely not shared with other divisions. For such scenarios, you specialize case type class names containing a division modifier. For example:

ORG-DIV-APP-[Work/Data/int]-"

My question is since applications are not being shared with other division why dont we create class structure like

ORG-APP1-[Work/Data/Int] ORG-APP2-[Work/Data/Int]. In this case we can keep the class name length in control and also reusable component will remain in ORG layer just like ORG-DIV-APP-[Work/Data/int]-

Please clarify what I am missing here

Pega Academy
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.