pyMode=Component means the Application rule should be treated as a collection of rulesets that serve a common purpose, plus does not define a workpool nor any case types.
An example Component could be a Library and its Functions, or a utility that encapsulates specific functionality. An example Component would be code that parses and transforms an HTML TABLE to CSV . In the LSA course, a Component was added to an Application to speed the development process. The Component contained a simple flow that begins by copying the pyWorkCover's most recently attached Data-Corr-Email instance to an embedded page. The Component then allows the Data-Corr-Email embedded page to be edited and resaved using a Rich Text Editor. The Component also supports automatically sending the email at a specific time.
A "Component Application" is something that meets the definition of a component by being highly reusable, has a documented interface, and has been well-tested The difference is that an Application Component would have its own workpool plus define one or, perhaps a few, case types, hence would be pyMode=Application.
Can I categorize multiple integration rulesets and include all those rulesets as part of a component? Basically I am planning to build a global integration layer which any project across the organization can just use them when they are included at the enterprise layer. I can do it in 3 ways
1) By creating single Global int layer which includes all the integration rulesets. The con I see with this approach is if one application has to consume latest X intgeration ruleset version , they are forced to consume all other latest A , B , C integration ruleset version as well
2) By categorizing integrations and creating multiple applications and use the MOB concept. Even with approach the con I mentioned above still exists but the impact is very minimal as we have multiple applications
3) By categorizing integrations and creating multiple components for each category , but i don't understand the differences between #1 and #2. What is the benefit I am getting in creating multiple components vs multiple applications?
Bottom line I am trying to establish a global foundation / enterprise layer for my organization. I just want to ensure that the path I take does not lead to heavy maintenance and the same time don't want to restrict all applications team to use the latest and greatest code even though they might not require
I was also told that Pega is moving away from Component Archietecture? Is it true?