When you design Email Treatments for bundles, consider the type of bundle. A typical Email Treatment for an action bundle includes an overall description of the bundle and details for each of its members. Additionally, based on the bundle type, response links can be provided at either or both the bundle and member level.
The top level BundleTemplate Email Treatment is provided as an out-of-the-box sample. The following figure shows a template email for sending a bundle of offers:
The BundleTemplate treatment includes the following parts of a bundle Email Treatment:
- Bundle name - References the .OfferData.BundleName property
- Response link for bundle – Added using the Insert Button functionality
- Impression capture - References the RecordImpression section. With bundles, you typically include the impression capture section at the parent level.
- Member details - References the BundleTemplate section. This section
uses the BundleOfferMembers page list property to display the member
actions in a grid with accept and reject response links for each member.
The BundleOfferMembers property is populated at runtime to contain details of the various bundle members. This can be used in dynamic containers such as the repeating grid. You can also make static references to member actions in this page list. For example, to display the name of the first action in the bundle, you reference the .BundleOfferMembers(1).OfferData.pyName property.
Another common usage pattern is to update the grid in the BundleTemplate (or equivalent) section at the top level, which is PegaMKT-Work-Offer, to include a sub-section for displaying relevant action information. For example, MemberOfferDetails. You can then create a top-level version of this section to serve as a base for all member actions. To customize the details for a particular issue or group, you must override the details section in the appropriate issue or group class.