Posted: 16 Jul 2015 2:17 EDT Last activity: 22 Jun 2016 0:48 EDT
Select Application Structure as Framework and Implementation
When we select the Application Structure as 'Framework and Implementation', what are the differences we have to make? Like where to create the various types of rules(sections, flow actions..). How to handle the different layers?
I'm quite new to Pega, so I would appreciate help.
When you select the "Framework and Implementation" option, the application wizard will create the application with both the framework and implementation layer. For example:
This allows you to build your application and rules in the framework layer. The Implementation layer rules will simply just be a wrapper that calls the rules in the framework layer. This allows you to create many implementations from the same framework of rules to specialise, e.g. SAE-EnggServices-Work, SAE-CorpServices-Work, which inherit rules from the framework layer.
This allows specialisation of the rules in the framework in each implementation layer.
Pega code is the whole house
Framework is like a living room (hall)
Implementations are like bed rooms.
If you want your TV to be accessible to all people in your house, you'd place that in your living room. But if don't, you have to put one tv in each room.
Same thing applies here. If you want any rule to be accessible by multiple implementations, you put it in framework. If you want to customize something, you can do it in any implementation. For ex, only one of your bedrooms need a tv but not all. In this case, you'll just buy another TV and put it in your room. People in other rooms will still access the TV in living room. If you have 1 framework and 5 implementations, and you need one customization, you just do it in one implementation layer. All other 4 implementations will use the rule(s) in framework layer.