Data Types Reuse Layer
While creating the application via Enterprise Application Wizard in Pega 7.1.9, we have an option to keep the data types in Enterprise or Framework or Implementation layer. What are the best practice around choosing the reuse layer especially Enterprise vs Framework layers?
Accepted Solution
Pegasystems Inc.
IN
Hi Gyan,
The enterprise class structure is an out-of-box structure to help facilitate reuse and specialization along class lines.
There are four layers, each dedicated to a particular kind of reuse.
The Organizational layer is intended to hold all rules that apply corporate wide.The kinds of rules most often encountered here are:
ï§ Security (for example, LDAP access, how users are granted rights, etc…)
ï§ Corporate Logos and Skins
ï§ Corporate wide data models (for example, Customer, Insured, etc…)
ï§ Some Integration Points (Access to a customer database is a good example of a potential organization wide integration.)
The division layer holds all the rules for a logical grouping within that business.The key is to identify if these rules span across different processes within the business.The kinds of rules most often encountered here are:
ï§ Division wide data models
ï§ Division wide letterheads, signature lines, office locations, telephone numbers, etc…
The framework layer is for most of the rules in an application.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 kinds of rules most often encountered here are:
ï§ Case types
ï§ Flows
ï§ Flow actions
ï§ Sections
Hi Gyan,
The enterprise class structure is an out-of-box structure to help facilitate reuse and specialization along class lines.
There are four layers, each dedicated to a particular kind of reuse.
The Organizational layer is intended to hold all rules that apply corporate wide.The kinds of rules most often encountered here are:
ï§ Security (for example, LDAP access, how users are granted rights, etc…)
ï§ Corporate Logos and Skins
ï§ Corporate wide data models (for example, Customer, Insured, etc…)
ï§ Some Integration Points (Access to a customer database is a good example of a potential organization wide integration.)
The division layer holds all the rules for a logical grouping within that business.The key is to identify if these rules span across different processes within the business.The kinds of rules most often encountered here are:
ï§ Division wide data models
ï§ Division wide letterheads, signature lines, office locations, telephone numbers, etc…
The framework layer is for most of the rules in an application.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 kinds of rules most often encountered here are:
ï§ Case types
ï§ Flows
ï§ Flow actions
ï§ Sections
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. The rules that are the most specific would exist here.One key aspect to the implementation layer is that this is where any of our work classes should be instantiated. This allows the class to be the most specific and can then ensure it’s leveraging the appropriate rule in all instances. It also keeps the work for a particular division tied to that one division and avoids possible cross division contamination of work.
The kinds of rules most often encountered here are:
ï§ Class groups
ï§ SLAs
ï§ Routers
Kind Regards,
Gisela