Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Designing Flows for Bundles

Updated on September 15, 2022

When designing flows for bundled items, the user must take into consideration the role of the action. For the parent action, the flow can also be tailored differently based on the bundle type.

Pega Customer Decision Hub
  • Configuring the bundle parent action

    The parent action flow is responsible for sending out the email containing details of the bundle and its members. This email can also contain links to respond to the bundle and/or individual actions. This initial responsibility is the same across all three bundle types. Once the email has been sent, the behavior of the parent action flow typically varies slightly based on the bundle type.

  • Configuring the bundle member actions

    The flow for a bundle member action differs slightly from typical action flows since the initial communication of the action has already been made by the bundle parent action. The flow also differs based on the bundle type.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us