Using Issues and Groups to store rules

Most Marketing rules can be categorized under the Issue and Group hierarchical levels. For a majority of these rules, the Issue and Group values also serve as logical abstractions of the Applies To class key (.pyClassName) of their respective rule. This key determines the class under which the corresponding rule instance is created.

The value for this key attribute is determined as follows:

• Top level rules - Top level rules are stored in the base Marketing offer class (PegaMKT-Work-Offer).
• Issue level rules - Issue level rules are stored in the class for their Issue, which resides under the base Marketing offer class. The Marketing application automatically creates this class when the first marketing rule is stored in the corresponding Issue. For example, for the Sales Issue, the class where Marketing rules are stored is: PegaMKT-Work-Offer-Sales.
• Group level rules - Group level rules are stored in the class for their Group, which resides under the class for their Issue, which resides under the base Marketing offer class. The Marketing application automatically creates this class (and, if necessary, the class for the parent Issue) when the first marketing rule is stored in the corresponding Group. For example, for the Handsets Group under the Sales Issue, the class where Marketing rules are stored is: PegaMKT-Work-Offer-Sales-Handsets.

The following Marketing rule types employ the above mechanism for storing their rule instances:

• Database/File Output Templates
• Email Treatments
• Passbook Treatments
• SMS Treatments
• Offers
• Volume Constraints

Pega Marketing Help Home