Why do we need a component when everything can be placed inside a framework layer and that can be extracted via implementation layer in pega?
Framework is specific to the application. For example In Claims Application, you can have Claims FW and you can build different flavors of the Claims Application for North America, Europe, Asia Regions.
Component is plug and play. You can build components and plugged into Claims App, Customer Service App, Onboarding application which can be reused across multiple apps.
Hello Tanya, components are meant for modular applications. So single purpose light weight modular apps can be added as needed.This enables loose coupling and aligns with Pega’s architectural shift.
Framework and implementation are tightly coupled, but a component is different. A component can be added to multiple applications and its functionalities can be reused across them.
In a component, we should not have any application-specific case types. Instead, only reusable functionalities should be created as components.
For example, if you build an integration rule for sending messages to users and place it inside an application’s integration ruleset, that functionality becomes specific to that application. It cannot be easily reused in other applications where the class structure may be completely different.
However, if the same functionality is built as a component, it can be reused across multiple applications and clients with minimal dependency on the underlying application structure. In component when you are building something have the rules class org value something specific to the functionality what you are building.