Dears
Component applicaton’s ruleset should not include a case type based on the article below.
However, quiz question part of Application design mission is not accepting the described answer in the article and feedback is showing that “component applications can contain case types”. Does anyone inform us related subject?
@m.caldag Hi Mert,
Component applications can contain case types.
You can create a case type in any application, but doing so in a component application would go against the purpose of creating a component application in the first place - namely a collection of reusable rules such as such as flows or correspondence rules, integration assets, or a function library.
So, yes, a component application can contain case types - it is a best practice for creating a component application that it does not contain case types.
@eddie.jm Hi Eddie, thanks for your answer. Nevertheless, I do believe that it would be better to add some validation rule which is going to prevent case type rule creation under component application’s rulesets.
@m.caldag Hi Mert,
I wanted to follow up on this and provide some clarity in case others read this post.
There is only an application in Pega, and an application can contain any of the available rules such as case types, data types, correspondences, integrations, etc. An application is an application - there is no functional option to make one application a component application - where we could then restrict the types of rules you could create in that application.
Component is an arbitrary name we use to describe an application that contains only reusable rules, or…components.
The goal of the topic is to help you understand the best practices for the decomposition of an application, and then how to organize the decomposed components into separate applications, depending on use.
Hope this helps clarify the meaning of a component application.
@eddie.jm Nice explanation thank you. I often create reusable rules under enterprise application which is used by other applications’ built on part rather than using component application approach. I do believe that we can achieve the same result when we use the built on application approach. Both ways are supporting one to many relationship with the respective application. What benefits are we gaining in case we use component? Could we say that there will be no auto generated classes and other type of rules created in the phase of application creation in component creation as a benefit?
