Skip to main content

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

Pega Foundation for Healthcare 8.1

Updated on October 14, 2021

Required Pega Foundation for Healthcare 8.1 hotfixes

Pega Foundation for Healthcare Hotfixes
Pega Platform Version Hotfix Number Observed Behavior
8.1.9HFix-67740In PFHC 8.1, security has been enhanced on a number of rules by the addition of an existing privilege "AllFlows".
8.1HFix-50778The use of a timestamp in setting the range key for a code set is producing collisions on a heavily loaded system, resulting in loss of data. This has been fixed this by modifying UpdateOrSplitCodeRange activity to use getCurrentTimeStampUnique() instead of getCurrentTimeStamp()
HFix-52044New properties added to plan data model to support accumulator related enhancements
HFix-53719New classes and properties are added to support enhanced flattening of PCS plan and product entities.
HFix-53934New property, BenefitLimitCountBy added to hold the BenefitLimitCountBy value configured in PCS limit , when a Product or Plan is flattened.
HFix-54373New property, BaseName added to hold BaseName value for flattened PCS PLAN and PRODUCT.
HFix-55346New properties included in flattening data model to support PCS data extract enhancements for inclusion of order of cost shares and formatted cost share amount text values for deductible and OOP calculation methods other than Embedded.

System 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:

Progress of plan level flattening, can be tracked.

In case of any failure, reprocess the plans in broken queues.

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

This activity “DELETEANDREFLATTENPLAN” is refactored to truncate the table instead of obj-browse and obj-delete by handle.

History class instances creation/inserts is disabled for flattened main classes to reduce the number of database interactions.

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

Close Deprecation Notice
Contact us