Skip to main content


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

Automatic update of plan bundles

Updated on April 12, 2021

The Plan Bundle Update feature in Pega Product Composer for Healthcare automatically updates all plan bundles in real time to reflect the new version of the plan. Using this feature results in time-saving for the operation teams.

Pega Product Composer for Healthcare Pega Product Composer for Healthcare

Customers bundle their healthcare products into a plan bundle for sales purposes. Most of these plans are open-ended, which means that there is no end date specified, but external factors can cause customers to change the end date. When customers configure a new version of a plan by modifying the plan end date, they must manually update every plan bundle that contains the plan so that the plan bundle has the latest version of the plan. By setting these parameters, you control the stages in which the plan bundle update occurs.

  1. In the header of Dev Studio, click ConfigureProduct composer systemConfiguration.
  2. Click the Flow settings tab.
  3. In the Automatic update for plan bundle section, select all check boxes in the Plan column to indicate the stages when you can configure a new plan version by modifying the plan end date.
  4. Select all check boxes in the Plan Bundle column to select one or more stages in which the automatic update of the plan bundle will occur.
    This update occurs only when a new version of its plan is configured by modifying the end date during a specified stage.
    For example: You have three different plans that are in three stages. All three plans belong to the same plan bundle. The automatic update for the plan bundle is set for the Implementation stage. This means that the plan bundle update occurs multiple times, each time that a new version of the plan is configured by modifying the end date of the plan during each of the three stages.
  5. When you finish your selections, click Actions > Save as system configuration.
    Saving the settings as personal configuration saves the changes only for the logged in user. To save the configuration as system settings, save the settings as system configuration.
What to do next:

For report information, see the Plan Bundle Update report in the Pega Product Composer for Healthcare reports section.

Configuring a plan bundle

In Pega Product Composer for Healthcare, a plan bundle is an aggregation of different stand-alone plans that are sold as one item. For example, a plan bundle might include specific medical, dental, vision, and pharmacy plans.

A fixed bundle is one where the products are always sold together. For example, when you enroll in ABC Medical, you automatically are enrolled in the plans that were configured in the bundle. A choice bundle means that you can add multiple plans of the same type, for example, medical, when you configure the plan bundle.

  1. In the l
  2. In the header of Dev Studio, click Launch portalProduct Development.
  3. eft navigation panel of your workspace, click NewPlan Bundle.
  4. Select a type of plan bundle, complete the information, and click Save or Continue.
  5. Select the plans that you want to include in the bundle.
    If you are configuring a choice plan bundle:
    1. Select the plans from the lists that will be part of the bundle, and click Add <plan>.
    2. Use the calendar widget to create a date of association.
      The association date is optional. It is the effective date for the specified plan in the plan bundle.
  6. Click Save to complete plan bundle at a later time or Continue.
  7. Review the details of your plan bundle, and then click Finish.

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