Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Pega Product Composer for Healthcare Hotfixes

Suggest edit Updated on September 10, 2021

The following tables list required hotfixes the Pega® Product Composer for Healthcare application requires. To request a hotfix, go to your account on My Support Portal. Click New request > For something I need and select Service request > Existing hot fix. Add and verify the hotfix details and click Finish.

Import each type of hotfix in the listed order during the Pega Product Composer for Healthcare installation or upgrade:

  • Apply Pega Platform hotfixes immediately after the Pega Platform installation or upgrade. 

  • Apply Pega Product Composer for Healthcare hotfixes just after you complete the application bundle import.

To see hotfix installation details, see the readme that is included in the hotfix.

Pega Product Composer for Healthcare 8.6

Required Pega Product Composer for Healthcare​ 8.6 hotfixes

Pega Platform VersionHotfix NumberObserved Behavior
8.6.1HFix-81244Node restart if background activity exceeds 15 mins.
8.6HFix-80632Misc fixes for UI, Performance and other items.

 

Pega Product Composer for Healthcare 8.3

Required Pega Product Composer for Healthcare​ 8.3 hotfixes

Pega Platform VersionHotfix NumberObserved Behavior
8.3.5HFix- 80651Node restart if background activity exceeds 15 mins.
8.3.4HFix-67736This hotfix delivers the B20 security update changes, in Pega Product Composer for Healthcare.
8.3.1HFix-61021Union data objects are not getting saved after 50 records because pagination is enabled in the report definition to page size as 50.
HFix-69395If Product is missing in the instance then the plan SU processing is routed to broken Queues, all SU locks are retained and not released.
HFix- 80382Create, update info is incorrect for entities created using SU.
HFix- 80241Benefit categories are not retained in Smart update.
HFix- 68656In SmartUpdate the Review coverages batch, is not showing the updated Deductible and OOP calculation method.
HFix- 68451

In Smartupdate “UpdateExisting” model type of BenefitSet go till the  ProductTemplate.

Now in ProductTemplate “UpdateExisting” model type, do select all see the target benefit details are remapped to original BenefitSet.

HFix- 61850In ProductTemplate “Default order of costshares” is cleared  when a new BenefitSet is selected and tree is Regenerated with “update only” checkbox and for regenerate new tree process pop up cancel is clicked and continued to next screen.
HFix- 61026For network/benefit/grouper nodes in the variation configuration screen, calculation method description is missing in UI for copay and coinsurance costshares.
8.3HFix- 59544

On upgrade to Pega Product Composer for Healthcare 8.3, when user runs this utility:

  1. The Annual and LifeTime max variations are copied to respective costshare fields.
  2. The variations created for annual and lifetime are deleted.
HFix-67704In Pega Product Composer for Healthcare Product or Plan when a node is opened, authorization is displayed as blank instead of showing the configured data.
HFix-66929SmartUpdate- 2 Enhancement wherein the smart update functionality, is extended for BenefitSet and Product Template as well.
HFix- 63512

This hotfix addresses below issues in SmartUpdate:

  1. Null PointerException” is observed, during plan clone creation.
  2. Utility to resolve issues with, withdrawn smartupdate entities.
  3. SmartUpdate plan created using “UpdateExisting” model type, has wrong product uniondata.
HFix-63658

Plan Flattening” is updated to use a single QueueProcessor, to improve the flattening speed.

    HFix-63773

    In plan smartupdate, corrected the “NullPointerException” caused due to “OrgProduct” reference.

    HFix-63865

    Added validation for “Missing Alias Name” issue, in smartupdate plans.

    HFix-63946

    Bypassed “History snapshots” creation, for the flattened class.

    HFix-63856

    Provided Fix for “WrongModeException” and “NullPointerException”, both in Flattening and SmartUpdate.

    HFix-64483

    In smart update, whenever the user navigates from product to plan and the model type is “Update current version”, all the plans of a product are not pre populated.

    HFix-64265

    Provided diagnostic patch for “Declare on Change”, not triggered issue.

    HFix-64696

    Below issues are fixed as part of this hotfix:

    1. In Plan SmartUpdate flow, corrected page used for “Covered/Required” flags.

    2. In case of SmartUpdate failure, union data are getting deleted.

    3. Missing AliasName” issue is observed, in smartupdate product and plans.

    HFix-63062 In the smart update flow, user is stopped with an error saying "there was an error in generating the version number".
    HFix-63122

    Below issues are addressed in this hotfix:

    1. In SmartUpdate Out of pocket and deductible ranges, are not copied correctly to Product/Plan for embedded calculation method.
    2. Pagination is enabled and capped at 50, for the report definition which fetches the union data records to be deleted.
    3. In SmartUpdate “Step down benefit” autocomplete, will now show all the benefits in the system.
    HFix-63168In SmartUpdate, tree regeneration is having issue when insert and move operations are performed on benefits.
    HFix-62926In SmartUpdate for Product/Plan flows, adding of “PolicyType”  CalculationMethod for Deductible and OOP across multiple batches, is adding duplicate rows in the smartupdated entity.
    HFix-62230Pre/Post extension rules, are provided for all  the SmartUpdate flowactions.
    HFix-62364PCS  Product save is resulting in error. These Products are created from ProductTemplates, having coverage configured at “Benefit” level.
    HFix-62423
    1. Performance issue is observed, when SmartUpdate Plan is run with large number of batches. 
    2. Allow SmartUpdates, when the built on entities of the current target entities are locked by other SmartUpdate.
    3. UI bug fixes for SmartUpdate flow.
    HFix-62719Customer is not able to resolve the “UpdateExisting” SmartUpdate objects, because of hardcoded class name.
    HFix-62794
    1. Status  of “Withdrawn” SmartUpdated work objects, is not updated.
    2. SmartUpdate coverage screen, is not loaded for “PolicyType” calculation method.
    HFix-62877In SmartUpdate , when more than one product are used for “UpdateExisting” , the plans retrieved are more in number than expected.
    HFix-61998PCS is enabled with SmartUpdate feature,  to update “Metadata/StructuralChanges/Coverages/AdditionalDetails” in bulk for Products and Plans.
    HFix-60771After upgrading from previous versions of PCS (which do not have benefit category feature) to PCS 8.3 (which has benefit category feature) customers are blocked on the benefits and grouper flows as they are forced to select ‘mandatory’ benefit category which is non-existent in the application. This fix makes it an optional field in all the PCS processes where it was originally mandatory.
    HFix-60594PCS flattening is failing when plan data class (PegaPCS-Data-Plan) is overridden at implementation layer. This fix implements the dynamic class referencing for plan data class in PCS flattening.
    HFix-60429Update date time information (“pxUpdateDateTime” property) is not correctly updated when the plan is updated as a result of dependent product update. This fix ensures that pxUpdateDateTime property is updated correctly.
    HFix-59061Data integrity issues are handled, which are observed when product/plan are being updated and flattening is triggered for the same Product/Plan.
    HFix-58820Edit button is now disabled for all the PCS entities, when they are in initiation stage and do not reach the Pending Approval stage.
    HFix-58537Changes are required to address the following PCS PlanBundle issues:
    1. Duplicate validation is fixed, when invalid plan is entered.
    2. In plan bundle “select plans” screen, plan selected through autocomplete is retained even when it is manually
      updated to an invalid plan.
    3. In Choice plan bundle, date icon is not displayed.
    4. Association date labels in plan bundle “select plans” screen, is updated to include FromDate and ToDate.

    Below validations for Association date are also introduced:

    1. AssociationToDate less than AssociationFromDate.
    2. AssociationDates are within plan bundled effective and end dates.
    HFix-58168For new BenefitSet and Groupers there will be no option to set the required flag for Benefit.
    In ProductTemplate /Product and Plan required flag will populate, on Benefit/Groupers from Network level but not from Benefitset.
    HFix-58055In ProductTemplate, go to Configure Benefits screen and launch a Benefit. In the Additonal Benefit Details tab, if you expand Documentation Support section, the Notes section is missing.
    HFix-57852 When Plans created in Pega Product Composer for Healthcare​ 7.31 are reiterated in Pega Product Composer for Healthcare​ 8.3, on click of Plan Metadata screen continue error is shown on UI.
    Note: This issue is addressed on upgrade to 
    Pega Product Composer for Healthcare​ 8.3 from Pega Product Composer for Healthcare​ 7.31.
    HFix-57245Label is changed for BenefitSet case, from Category to Insurance Line.
    HFix-57069For ProductTemplate/Product/Plan flows in the Configure benefit categories screen, if a Benefit category contains more than 10 benefits, then it does not show all benefits.
    HFix-57079

    This SE addresses the below Known Issues, Enhancements and  Exceptions:

    1.  Create a producttemplate and create product and plans from it. Now create copy from entities, for already created product and plans. Now run massupdate for producttemplate, in the target list screen the copied entities of product and plan are not retrieved.

    2. Flattened result (and data extracts) of product and plans is enhanced to include a new property to show the Network level covered/not covered/required/not required indicators.

    3. Mass update of product template/product and plans is enhanced to have an option to edit covered and required fields in “update used” and “add used scenarios”.

    4. An issue is fixed to not show up the products in the target selection (under the product templates) screen that didn’t have the benefits that are being updated in the Mass update “update used scenario”.

    5. Fix is given to address the issue of large volume of plans, going to the broken queue when flattening utility is executed.

    6. An exception is fixed, when a specific network is selected in the ‘target selection’ screen and ‘Run massupdate’ button is clicked  for Mass update of Product and Plan ‘Update used benefit inside a grouper’ scenario.

    This exception will not occur if ‘All networks’ is selected in the target selection screen.

    Known issues of 8.3

    1. Benefit desc­­ription did not get updated, when codes are entered manually in Benefit mapping screen. Fix is given to update the Benefit desc­­ription, when codes are entered manually in Benefit mapping screen.

    2.In Choice Planbundle, validation message was not displayed when invalid plan is selected. Now validation will be thrown, when invalid plan is selected.

    3.  When Plan benefit Lifetimemaximum/Outofpocket/Annualmaximum/Deductible/Limit/Eligibility cost shares are inherited from Product benefit, on click of restore at Plan benefit blank section was displayed. Change is done to hide
    the blank section.

    4. "Invalid benefit selected" error message was displayed, even though correct Benefit is entered in Copy From Flow of Benefit. This issue is fixed now.

    Other issues:

    1. In Massupdate Benefitset ‘remove used’ operation is first selected and  user goes to second screen. Now if user comes back ,to the first screen in Mass update and  operation is changed to Add’ from ‘Remove’ and user proceeds to second screen again then "At least one benefit category must be added" message is displayed.­­­ This issue is fixed now.

    2.  For MassUpdate BenefitSet ‘Remove Benefit’ scenario, InvalidParameter exception was thrown when navigating to configure data screen. Changes are done to handle this exception properly.

    3. For entities created using CopyFrom, MassUpdate ‘Remove scenario of Benefit’ was not removing the Benefit properly from the copied entity. Change is done to remove benefit completely from the copied entity.

    4.  When ProductTemplate is Massupdated twice and a Product is created from this ProductTemplate, then Product Benefit costshares are displayed as “0”. Fix is given to correctly populate the Product costshares.

    5. Benefit category "Where referenced" option, was not showing the Benefits which consumed a particular Benefit Category. Code is updated to show Benefits, in BenefitCategory where reference option.

    Pega Product Composer for Healthcare 8.2

    Required Pega Product Composer for Healthcare​ 8.2 hotfixes

    Pega Platform VersionHotfix NumberObserved Behavior
    8.2.2HFix-53833This hotfix provides the compatibility to upgrade Pega Product Composer for Healthcare application from version 8.1 to 8.2.

     

    Pega Product Composer for Healthcare 8.1

    Required Pega Product Composer for Healthcare​ 8.1 hotfixes

    Pega Platform VersionHotfix NumberObserved Behavior
    8.1.6HFix-58275System becomes unresponsive when bulk plan flattening, is attempted using  “PCSFlattenAllPlansAfterDeleting”  activity. As part of fix Queue-Method is replaced with queue for processor so that:
    1. Progress of plan level flattening, can be tracked.
    2. In case of any failure, reprocess the plans in broken queues.
    3. Control the parallel execution of plan flattening (by defining the appropriate number of threads in queue processor rule: “CREATEFLATTENEDPLAN” (which is defaulted to 1 thread on the queue-processor).
    4. This activity “DELETEANDREFLATTENPLAN” is refactored to truncate the table instead of obj-browse and obj-delete by handle.
    5. History class instances creation/inserts is disabled for flattened main classes to reduce the number of database interactions. 
    8.1.1HFix-56322

    This SE addresses the below MU/Flattening issues and enhancements:

    1. Create a producttemplate and create product and plans from it. Now create copy from entities, for already created product and plans. Now run massupdate for producttemplate, in the target list screen the copied entities of product and plan are not retrieved.
    2. Flattened result (and data extracts) of product and plans is enhanced to include a new property to show the Network level covered/not covered/required/not required indicators.

    3. Mass update of product template/product and plans is enhanced to have an option to edit covered and required fields in “update used” and “add used scenarios”.

    4. An issue is fixed to not show up the products in the target selection (under the product templates) screen that didn’t have the benefits that are being updated in the Mass update “update used scenario”.

    HFix-56291Fix is given to address the issue of large volume of plans, going to the broken queue when flattening utility is executed.
    HFix-55352Excel data extract feature is enhanced to include the following order of cost shares changes:
    1. Addition of 4 new columns in the Product and Plan summary and cost share report excel template.
    2. Four new columns have been added in the DB table.
    3. Necessary code changes were done to populate the above mentioned columns.
    Below fix is applied to the Excel data extract feature to address all the calculation methods (DED/OOP):
    1. Addition of 1 new column in the Product template, Product and Plan summary and Product and Plan cost share report excel template.
    2. One new column have been added in the DB table.
    HFix-54810Excel data extract feature is enhanced to populate the data into a dedicated data base table.
    HFix-54364Below is the list of PCS Performance improvement changes:
    • PCS Flattened Product/Plan  has BaseName flattened. Fix for Effective/Term Dates not shown in PCS Network flow.
    • Added Filter in Product Template/Product/Plan DataExtract ReportDefinitions, to remove the Rejected entities from the
      Data Extract Search results.
    • Create a Product Template and configure order of cost shares/accumulator/authorization at benefit level. 
      Now create a Product using this Product Template ,error is  thrown at configure benefits screen on click of Mark all complete.
    • Made changes to save/update, Covered or not covered flags while doing save across networks in Grouper and Benefit node,
      in configure benefit screen of Product Template /Product/Plan flows.
    • In Product Template flow go to costshares and accumulators screen, Orderofcostshares flag was made editable.
    • User is not able to edit cross network accumulator at Plan network level.
    HFix-53955Enhancement for Limit configuration by adding new option BenefitLimitCountBy and Numberofdays option in units across every ProductTemplate/Product/Plan flows.
    HFix-53922This hotfix provides enhanced Covered/NotCovered functionality across PCS ProductTemplate/Product/Plan flows.
    HFix-53478Plan and Product detailed Cost Share Reports.
    HFix-53444Data Extract Changes: The data entered into PCS system may have to be validated manually or using external tools. To facilitate this, the data configured should be extracted to excel sheets, for consumption/validation in the downstream systems. In the absence of this data extract, the plans created must be manually verified to certify the data entered in the creation process.
    HFix-53311Below is the list of PCS Performance improvement changes:
    • A new work type is created to handle Auto updating and flattening of Plan for Product Change .
    • The embedded page property ‘OrgProduct’ of class ‘PegaPCS-Data-Plan’, which was earlier of type ‘manual data access’, is updated to refer a data page that holds the product data.
    • To address SR-D8613, plan code is updated to handle the junk data entered in the copy from field.
    • PCS performance can be further improved by removing unused indexes and few unused properties.
    HFix-53216For some PCS plans flattening process is failing with IndexOutOfBoundsException error.
    HFix-52882RUF for union data retrieval mechanism is updated to replace Page copy with property set to improve performance for ProductTemplate/Product/Plan flows.
    HFix-52816Click on the action menu on a case from the case type landing page search results.This creates a case of the base application layer because it is hard coded instead of using DCR.
    HFix-52777A small subset of PCS Plan work objects are not creating corresponding Plan data instances upon approval step.
    HFix-52746Post processing of "Configure Benefits" screen flow is slow for PCS ProductTemplate, Product, and Plan flow.
    HFix-52726Excellus has approximately 2200 plans that contain corrupted data. They could be corrected by opening and re-saving each but that will take a long time to do it individually for each plan. Utility to remove unused duplicate pages in plans (OrgProduct, BenefitTree).
    HFix-52673Below is the list of PCS Performance improvement changes:
    • Remove duplicate orgproduct.
    • Remove duplicate BenefitTree.
    • Removed coverage and non coverage mapping groups.
    • Remove temporary pages present in the clipboard.
    • Fix in PCS flattening utility to address issue with BenefitSummary record generation using multiple threads.
    • A Utility is provided  to remove the above list of items from the existing PCS entities to improve flattening response time.
    HFix-52231In the Product flow metadata screen, deletion of Market Segment is deleting the newly added coverage levels.
    HFix-51782When creating a Plan and proceeding to the "Configure Benefits" screen, Benefits inside a Grouper do not show correct values for cost share which are configured at parent Product. Inheritance description is correct and when opening the benefit correct cost share values show.
    HFix-51629In PCS for Product Template/Product or Plan, go to Configure Benefit screen. Try to configure Limit , it provides  option to select step down benefit. For few of the benefits after selection the benefit description disappears.
    HFix-51467Performance issue is occurring when trying to open/edit the benefits inside a grouper. Also noticed that the couple of  products  had five networks.
    HFix-51419Running of PCS flattening utility for Plans, results in times out issue.
    HFix-50735In PCS plan flow unable to complete creation of a plan because an error is thrown on selection of non existing product.
    HFix-50370Performance issue is observed in Pega Product Composer for Healthcare application, when edit is clicked in grouper/benefits configure cost share screen for Product flow.
    8.1HFix-51594Changes are required to address the following issues:
    • Code is not sent as part of search criteria, so if there are more than 1000 records for a service type then it is not fetch in the results.
    • In PCS Product template/Product/Plan flows if blank cost share is entered in configure Network/Benefit Details Screen it throws error and after click on save error is not retained and the entity can be saved with blank value for cost shares.
    • In PCS Grouper flow under Actions button there is option for where referenced, on click it shows blank but if the grouper is consumed in Benefit set/Product template/Product/Plan that list should show up.
    HFix-49276Changes are required to address the following issues:
    • In Mass Update 1st screen for Benefit Set, PT, PRD , PLN flows junk character validations should be thrown in the autocompletes.
    • Added validation to avoid spaces and special characters in code set/grp names in PCS configuration page.
    • Dental coverage details are not displayed in Benefit Mapping screen, while adding individual CDT codes.
    • In PCS sample manager portal, duplicate row entries are seen for reports, example “Plans Per Product Drill Down”.
    • In PT Configure benefits screen, grouper name is not a linked key.

     

    Pega Product Composer for Healthcare 7.31

    Required Pega Platform hotfixes for Pega Product Composer for Healthcare 7.31

    Pega Platform VersionHotfix NumberObserved Behavior
    7.3HFix-36013Linkey key property does not get resolved on the user interface.
    HFix-36058When a repeating dynamic layout has more than one record in its list, the autocomplete value selected in any of the list records is set to first record in the list.
    HFix-35720The new application wizard does not work with locked rulesets. This can result in exceptions while propagating data to subcases in the implementation layer.

     

    Required Pega Product Composer for Healthcare​ 7.31 hotfixes

    Pega Platform VersionHotfix NumberObserved Behavior
    7.4HFix-45910This hotfix provides compatibility support to Pega Product Composer for Healthcare 7.31 with Pega Foundation for Healthcare 7.4 on Pega 7.4.
    HFix-44385This hotfix provides compatibility support to Pega Product Composer for Healthcare 7.31 with Pega Foundation for Healthcare 7.31, which includes the following issues:
    • For the entity opened from search, the tab name is displayed as 'New', instead the entity's name.
    • Close icon is displayed only for the latest tab.
    HFix-44236This hotfix provides compatibility support to Pega Product Composer for Healthcare 7.31 with Pega Foundation for Healthcare 7.4, which includes the following issues:
    • For the entity opened from search, the tab name is displayed as 'New', instead the entity's name.
    • Close icon is displayed only for the latest tab.
    • On click of pulse icon overlay did not show up.
    • Approval option is not available to Actions list on Approval screen.
    • Left navigation does not collapse.
    7.3.1HFix-43299Cost share condition is failing while comparing the string for the Maximums costshare type.
    HFix-43171Deductible and out of pocket drop down values disappear when the user changed the Deductible and Out of Pocket calculation methods.
    HFix-43159While creating plan user modifies the section of creation then set link disappears on the screen.
    HFix-42927Cost Shares are effecting dropdown values while enabling and disabling checkbox.
    HFix-42926When the product is renewed using bulk-renewal then review screen is showing wrong category.
    HFix-42854Benefitsets dropdown is fetching all the records irrespective of the category selected while creating benefit from re-usable entities.
    HFix-42750EffectiveDate and TermDate properties are not present in the baseclass after application upgrade to PCS 7.31.
    Note: This hotfix is applicable only for upgrade from 7.12 to 7.31.
    HFix-42191This hotfix resolves the claim adjudication issues of Pega Product Composer for Healthcare application.
    HFix-41853Product Family property is shown duplicate on PRD Meta Page.
    HFix-41653Validation for OOTB Required fields are not working as expected for Product Template screen.
    HFix-41559Hotfix changes required for Post GA application Pega Product Composer for Healthcare 7.31.
    HFix-41430Prerequisite hotfix to support hotfix manager for Pega Product Composer for Healthcare 7.31.
    HFix-41275Issues while adding invalid grouper name in benefit set.
    HFix-41274Benefit name is getting truncated in review mode for benefitset in IE browser.
    HFix-41231Bulk Renewal issue for Grouper and Benefitset.
    HFix-38156Changes are required to support Pega Product Composer for Healthcare 7.22 upgrade to Pega Product Composer for Healthcare 7.31.
    7.3HFix-51157For Mass Update add used grouper flow, after the grouper is added incorrect union data key is generated.
    HFix-51090In PCS plan flow unable to complete creation of a plan because an error is thrown on selection of non existing product.
    HFix-46669Summary Plan Description is missing after upgrade.
    HFix-45937Resume Update any PCS flow, special character validation is not triggered.
    HFix-45540Alis Name is not allowing parenthesis character.
    HFix-45346In Plan flow Network Cost Shares screen, edit all costshares followed by uncheck costshares which are previously configured as Not Applicable, disables dropdown.
    HFix-45264Additional Benefit Details property values are not loading correctly for the Product rule object when opened from search screen.
    HFix-45228In Product flow cost shares screen, when same value for Default Order Of Cost Shares is selected the entire screen turns read only.
    HFix-43299Cost share condition is failing while comparing the string for the Maximums costshare type.
    HFix-43171Deductible and out of pocket drop down values disappear when the user changed the Deductible and Out of Pocket calculation methods.
    HFix-43159While creating plan user modifies the section of creation then set link disappears on the screen.
    HFix-43047Accumulators configured in Pega Product Composer for Healthcare are not populated in flattened Pega Foundation for Healthcare instance.
    HFix-42927Cost Shares are effecting dropdown values while enabling and disabling checkbox.
    HFix-42926When the product is renewed using bulk-renewal then review screen is showing wrong category.
    HFix-42854Benefitsets dropdown is fetching all the records irrespective of the category selected while creating benefit from re-usable entities.
    HFix-42750EffectiveDate and TermDate properties are not present in the baseclass after application upgrade to PCS 7.31.
    Note: This hotfix is applicable only for upgrade from 7.12 to 7.31.
    HFix-41853Product Family property is shown duplicate on PRD Meta Page.
    HFix-41744Need to extend the search capability for non approved entities.
    HFix-41653Validation for OOTB Required fields are not working as expected for Product Template screen.
    HFix-41559Hotfix changes required for Post GA application Pega Product Composer for Healthcare 7.31.
    HFix-41430Prerequisite hotfix to support hotfix manager for Pega Product Composer for Healthcare 7.31.
    HFix-41275Issues while adding invalid grouper name in benefit set.
    HFix-41274Benefit name is getting truncated in review mode for benefitset in IE browser.
    HFix-41231Bulk Renewal issue for Grouper and Benefitset.
    HFix-38156Changes are required to support Pega Product Composer for Healthcare 7.22 upgrade to Pega Product Composer for Healthcare 7.31.
    HFix-36058When a repeating dynamic layout has more than one record in its list, the autocomplete value selected in any of the list records is set to first record in the list.
    HFIX-36013Linkey key property does not get resolved on the user interface.
    HFix-35720The new application wizard does not work with locked rulesets. This can result in exceptions while propagating data to subcases in the implementation layer.

    Pega Product Composer for Healthcare 7.22

    Required Pega Product Composer for Healthcare​ 7.22 hotfixes

    Pega Platform VersionHotfix NumberObserved Behavior
    7.3HFix-31025Enhancements are required to overcome a compatibility issue with the Pega 7.2.2 platform release.
    7.2.2
    HFix-31025
    Enhancements are required to overcome a compatibility issue with the Pega 7.2.2 platform release.
    HFix-33850
    Changes are required to make Pega Product Composer for Healthcare 7.22 compatible with Pega Foundation for Healthcare 7.23.
    HFix-35825Product Development operator is unable to process work from the Initiation work basket.
    HFix-36813The list of benefit mappings in Pega Product Composer for Healthcare 7.22 must include Provider Specialty and Provider Type code set class.
    HFix-36959Changes to the Pega Product Composer for Healthcare 7.22 plan flattened structure are required to add a missing required service and service attributes and update the incorrect benefit end date.
    HFix-36969

    Updates the Pega Product Composer for Healthcare application rule to use Pega Foundation for Healthcare version 7.23. This hotfix only applies to installing Pega Product Composer for Healthcare 7.22 on Pega Foundation for Healthcare 7.23.

    Important: This hotfix must be applied after you apply HFix-33850.

    7.2.1
    HFix-32727
    A benefit variation is not displayed on a plan data instance.
    HFix-34142
    Application cannot retrieve codes when the code count is greater than 10000 in benefit mapping definitions.
    HFix-34411
    Changes are required to address the following issues:
    • Application incorrectly identifyies benefits as "duplicate" in Benefit Set flow while adding benefits to it.
    • User is unable to see the work items in the work basket list when trying to see them via the “See all” link on the work baskets section of user portals.
    HFix-35825Product Development operator is unable to process work from the Initiation work basket.

     

    Tags

    System Architect Lead System Architect Business Architect UX Developer Project Manager System/Cloud Ops Administrator
    Did you find this content helpful? YesNo

    100% found this useful

    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.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us