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.

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.

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.

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

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

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

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

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

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.

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

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.

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.

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.

1. Status  of “Withdrawn” SmartUpdated work objects, is not updated.
2. SmartUpdate coverage screen, is not loaded for “PolicyType” calculation method.

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.

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.

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. 

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”.

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.

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.

• 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.

• 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.

• 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.

• 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.

• 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.