Difference between Framework and application in PRPC terms
While creating a new application in PRPC, we can select differnet application strucutures like Framework only or Impementation only or Framework and Impementation, wanted to understand the extract difference between Framework only or Impementation only apart from the reusability.
Is there any any difference in the way either the Framework only or Impementation only or Framework and Impementation are created.
Does PRPC create any underlying rules for differently for differnet application strucutures
Framework created as part of Framework only is same as that created as part of Framework and Impementation application strucuture.
***Updated by Moderator: Vidyaranjan. Removed user added Ask the Expert tag. Apologies for confusion, shouldn't have been an end-user option***
An enterprise-level PRPC application typically consists of three parts: PRPC itself, a Framework layer, and an Implementation layer.
The Framework layer consists of generic applications. A Pega Business Process Solution contains templates for various functions within a specific industry or area of focus, intended for use as all or part of the framework layer of an enterprise application. Use of a Pega Business Process Solution can significantly reduce development effort by providing pre-built processes, user interfaces, data elements, and even entire cases for common business tasks in industries such as financial services, health care, and life sciences.
We can adapt a framework to a specific business’ needs by creating an Implementation application. In this layer, we refine only the functionality that requires changing, leaving the remaining functionality as-is. Because the functionality in the Implementation layer overrides the functionality in the Framework layer, our complete application includes a mixture of rules from each layer.
I hope this information will give an idea of what exactly do you mean by Framework and Application.
PRPC Enterprise Class structure generates four layers , they are:
· Organization Layer
· Division Layer
· Framework Layer
The Organization Layer
The organization layer exists at the very top of our enterprise class structure. This layer is intended to hold all rules that apply corporate wide.
The Division Layer
The division layer exists to hold all the rules for a logical grouping within that business. Most often, this is based on the line of business, but it is not restricted to that and instead could be regions, brands, or departments. The key is to identify if these rules span across different processes within the business.
The Framework Layer
The framework layer is all about the process. This is what empowers an organization to achieve the majority of their reuse. Processes within an organization are often very similar between the different divisions. By placing this common process in a framework, we just have to build it once for all the different applications within that organization.
The Implementation Layer
The implementation layer is where it all comes together. This layer is the application that a user leverages to perform their tasks. You can think of it as the ‘glue’ that holds together the rules from the framework, organization and division layers.
I have also attached visual diagram which would be helpful to understand how the Enterprise class structure works in PRPC and also helpful to choose the suitable layer on which you can build your new application.
Please go through that and let me know if it helps you.