PRPC 74 LSA Course :DESIGNING FOR SPECIALIZATION
Hi Pega Folks,
PRPC 74 LSA Course :DESIGNING FOR SPECIALIZATION >> Specialization use cases >> Use case: Define the product at the enterprise level
I am trying to understand the recommended solution for one of the scenarios.
3Phase Inc. is a large electronics manufacturing company that has been in business for 25 years. Over time, the ability of the company to stock new products and replacement parts has become increasingly complex. To manage this issue, the company created a separate Supply Chain Management (SCM) division. Currently, there is no need to specialize SCM applications by region.
Recommended solution no 3:
- Create a new application specific to the region. You create a wrapper application built on the existing application. Then, you create a new implementation application built on the existing application.
Can someone explain me the above in layman terms.
Pegasystems Inc.
US
The requirements suggest there are two possible ways to specialize the application, i.e., by division and by region, but as stated, region specialization does not make sense.
The SCM division needs to support multiple regions; it does not want to switch applications in doing so. The existing application's work pool class need not change.
One way is to create applications built on an existing application. The new application would contain Division-specific modifications. The work pool class currently does not contain a DIV namespace specialization, e.g., ORG-DIV-APP. Nonetheless the application can be specialized by the SCM division using ruleset resolution.
If the SCM division were already the "owner" of the application they would not not need to do this. They can simply continue to modify the existing application-layer code that they, themselves, own.
The SCM Division is free to define their own Division layer to house code that can be reused by any SCM Division-specific application. The Division reuse layer would be built on top of the Enterprise layer.