When designing Email Treatments for bundles, the user needs to consider the type of the 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 the bundle and/or the member level.

The top level BundleTemplate Email Treatment is provided as an out-of-the-box sample.

This treatment includes the following salient pieces 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, it is typical to 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. Users 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, 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 (PegaMKT-Work-Offer) to include a sub-section for displaying relevant action information, say MemberOfferDetails. Users 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, the user simply needs to override the details section in the appropriate issue or group class.