Skip to main content


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

Issues addressed in this version

Updated on May 4, 2021

This table describes issues resolved in this release that are of the most interest to and are likely to have the most impact on the Pega user and developer community.

Pega Product Composer for Healthcare Release Notes

The following ID reference is used:

  • Reference numbers beginning with “ISSUE ” or “BUG” refer to bugs logged in the Pega issue-tracking system.
  • Reference numbers beginning with “INC-” or “SR-” refer to corresponding Support Requests logged in My Support Portal.
Issue IDTitle and Description
BUG-636094In the PCS import wizard, after downloading the Microsoft Excel template for a particular entity type, for example, a benefit, you cannot download it again for the same or a different entity type.
BUG-643817When the same benefit is offered in both a carve-out and a participating network of the product template, the product clone created in the smart update process does not show the benefits in the carve-out network. This is a user interface issue.
ISSUE-89529You can create multiple SBC templates with the same name. There is no duplicate name check in place. The templates with the duplicate names will remain distinct from each other with regard to their other configured data.
BUG-640058When you edit a benefit within a product template, product, or plan and encounter a validation error while trying to save across networks, you cannot collapse or expand the networks.
  • BUG-613159
  • BUG-605347
  • BUG-640899
Formatting limitations related to Summary of Benefit and Coverage (SBC) documents
Tip: You can look up Pega Platform resolved issues in the Pega Platform Resolved Issues.

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