Class of rules packaged in a component
I create a Component to send an email, which can be re-used across multiple divisions of the same company XYZ . What should be the class of the rules which are being packaged as part of the Component Rule ? I went through the Email Component found in the LSA Course, and it seems that the rules in EmailEditor_20170814T145312970 ruleset have been saved in default PEGA Classes like Work-,@baseclass and Data-Corr-Email.
Is this a recommendation of the way things should be done for component-level rules?
Accepted Solution
Pegasystems Inc.
US
If you want to develop a pyMode=Component component, meaning it does not include any case types or workpool, and the code is completely generic to ANY application, then you can use Applies-To classes such as Work-, Data-, and @baseclass.
If a component is a unique combination of Work-, Data-, and @baseclass rules, there is no need to define a more specific Applies-To class.
Perhaps you could place rules in an enterprise-level ruleset with an Applies-To classes of Org-, but why do so if there is no need? Plus, you may want to submit your design someday to Pega Marketplace: https://community.pega.com/contribute-pega-marketplace
or just share it with the LSA Community.
One issue you could run into is the ability to define Relevant Records at the Work- and Data- level. You can try using pxSetRelevantRecord as mentioned in the LSA course.