Skip to main content
LinkedIn
Copied!

Table of Contents

Action Bundle Types

Version:

Only available versions of this content are shown in the dropdown

The system supports three modes of action bundling. These modes are henceforth referred to as bundle types.

  • Fixed Bundle - This bundle type should be used when customers must purchase the bundle in its entirety (all members). In this mode, the parent flow is the only flow that is processed. All Interaction History (IH) records are recorded for the parent bundle and all of its members. Any response will progress the parent flow.
  • Flexible Bundle - This bundle type should be used when customers can purchase the entire bundle or can pick individual members to purchase. In this mode, the parent flow is used as a container for distributing communication about the collection of offerings. A response to an individual offering will only start that member's flow. Any IH recording in the member flow will record information for the member action and the parent action. Responding directly to the parent bundle action will trigger all member actions that haven't been started. However, the parent flow will not progress.
  • Grouped actions - This bundle type should be used when the user has a selection of actions they wish to market together to the customer. The individual actions themselves may not have any correlation to each other. In this mode, (similar to the flexible bundle mode) the parent flow is used as a container for distributing communication about the collection of offerings. A response to an individual offering will only start that member's flow. However, unlike a flexible bundle, any IH recording in the member flow will only record information for the member action. Responding directly to the parent bundle action will not start any of the member actions, but will progress the parent flow.

The differences in the behaviors of the three bundle types are summarized in the table below:

Scenario Fixed Bundle Flexible Bundle Grouped Actions
Action initiation

Same behavior for all three bundle types:

- Start the parent flow

- Record initial IH entry for parent and all members

Respond to Email link for bundle (all members) - Resume the parent flow

- Start all member flows that haven’t been started

- Parent flow does not resume

- Resume the parent flow
Respond to Email link for individual action - Resume the parent flow - Start or resume the member flow - Start or resume the member flow
Update Status shape in parent action - Record IH response for parent and all members - Record IH response for parent and member actions that haven’t been started - Record IH response for parent and member actions that haven’t been started
Update Status shape in member action N/A (since member action is never started) - Record IH response for member and its parent - Record IH response for member only
Parent action completion - Complete parent and all member actions - Complete parent and member actions that haven’t been started - Complete parent and member actions that haven’t been started
Member action completion N/A (since member action is never started) - Complete member action only - Complete member action only
Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us