Upgrading from earlier versions of Pega Product Composer for Healthcare
Pega recommends that you avoid certain use cases during an update. For a list of common use cases to avoid for any Pega application, see Common use cases to consider during an upgrade.
Avoid the following Pega Product Composer for Healthcare use cases during an update:
- Managers should not attempt to approve any entities, such as benefits.
- Do not run the document generation wizard, because the Existing SBC template column will be blank for the selected products and plans.
- Do not submit a document generation work object for approval because the work status remains at Pending-Validate and does not continue to approval, even after the update is complete.
After the update, you need to re-index the products and plans.
For additional post upgrade steps please refer upgrade section in the implementation guide.
Variation indicator
Pega Product Composer for Healthcare version 8.7 introduces the variation indicator feature. After an update, the variation count is displayed for any product template, product, or plan entities that are pending approval or which were in-progress in the earlier version of Pega Product Composer for Healthcare. There is no separate utility that is available out of the box to update already approved entities. Run the existing entities through Smart Update to update existing entities that have approved status, so that they display the variation count. Begin the Smart Update case at the Product Template and select Update existing. You do not need to create batches. Smart Update automatically references the Products associated with the Product Templates, and then, as you advance through the Products, the Plans are automatically referenced. Once the Smart Update case is approved and resolved, the variation indicator is displayed on the entities.
When you run the Smart Update case it requires time to process the many entities involved. If necessary, run multiple Smart Update cases to divide the entities into smaller chunks. However, note that by starting with the Product Template and updating existing entities, Smart Update requires the children Products and Plans to be updated in the same case.
For additional post upgrade steps please refer upgrade.
Previous topic Known issues in this version