Hotfixes

CC-4320, CC-4326, CC-4327

If a customer had the Patient Journey Navigator accelerator already installed in their Salesforce org and then tried to upgrade to the Care Connect product in the same Salesforce org, they would run into a duplicate field selected error. This is because some field names from the accelerator were being referenced as internal fields when they should not be.

Field names in the accelerator and the product have been unified such that those in the former with the PJN prefix will be converted to their equivalent in the latter with the mvn namespace prefix. This means these legacy fields will be ignored in any future queries.

Fall '25 (V5.0.0)

Fall '25 (V5.0.1)

CC-4338

If a Salesforce org has a Care Plan (Case) record with over 200 open or closed Activity (Case) records, open activities may appear missing from the Additional Activities section in the Care Plan Timeline (pjnCarePlanTimeline) component on the Care Plan record page. For example, if a user creates a new activity for a care plan with more than 200 activities, the new open activity may not appear in the timeline, even if the user confirms that the new activity was saved successfully. This is because Salesforce limits subqueries to 200 child records.

Care plans and child cases are queried separately to avoid exceeding Salesforce's SOQL query limits.

Fall '25 (V5.0.1)

Fall '25 (V5.0.2)

CC-4368

The Care Plan Highlighted Fields (pjnCarePlanHighlightedFields) component was not displaying the API field values configured in the Care Plan Field (mvn__PJN_Care_Plan_Field__mdt) metadata record because the query did not reference the Problem (HealthCloudGA__CarePlanProblem__c) field set.

Fields added to the Problem (HealthCloudGA__CarePlanProblem__c) field set are now automatically queried and displayed in the care plan user interface.

Fall '25 (V5.0.1)

Fall '25 (V5.0.2)

PJN-2045, PJN-3957

When relationship roles were configured for the care team members on a care plan and an account was related to more than one contact, all of the related contacts were automatically assigned the same relationship role for the account. In other words, if two or more Relationship Role Configuration (mvn__PJN_Relationship_Role_Configuration__mdt) metadata records looked up to the same Case Field Configuration (mvn__PJN_Case_Field_Configuration__mdt) metadata record, all of the relationships that were created from the configurations were given the same role, even if specific reciprocal roles existed for each combination.

Relationships created from custom configurations via the Case field Configuration and Relationship Role Configuration custom metadata types will have the correct roles. Additionally, Care Connect will check for and prevent invalid relationships from being created, such as those without a set role.

Spring '25 (V4.0.0)

Spring '25 (V4.0.1)

PJN-3976

Activities that were added to a care plan from the Care Plan Timeline (pjnCarePlanTimeline) component, whether to a specific care plan stage or to the overall care plan, did not inherit the parent care program. In other words, the Activity (Case) records were not stamped with the Program (mvn__PJN_Program__c) value from the parent Care Plan (Case) record for the related Care Program (CareProgram) record.

Activities that are added to a care plan from the Care Plan Timeline component will inherit the care plan's program and program developer name.

Spring '25 (V4.0.0)

Spring '25 (V4.0.1)

PJN-3978

The electronic prescription enrollment (eRX) feature could not be used in Salesforce environments where Shield Platform Encryption was enabled because the eRX deduplication logic filtered on fields that could be encrypted but encrypted fields cannot be filtered on.

The eRX feature can now be used in orgs with Shield Platform Encryption because the eRX deduplication logic has been updated with post-query filtering for encrypted fields.

Spring '25 (V4.0.0)

Spring '25 (V4.0.1)

CC-4294

The New Additional Activity Button Override (mvn__PJN_New_Addtnl_Activity_Button_Override__c) field on the the Program (mvn__PJN_Program__mdt) custom metadata type did not properly add or configure the New Activity buttons in the Additional Activities section of the Care Plan Timeline (pjnCarePlanTimeline) component.

The Care Plan Timeline component has been refactored and updated to support the configuration of new additional activities via the New Additional Activity Button Override field.

Spring '25 (V4.0.1)

Spring '25 (V4.0.2)

CC-4320, CC-4326, CC-4327

If a customer had the Patient Journey Navigator accelerator already installed in their Salesforce org and then tried to upgrade to the Care Connect product in the same Salesforce org, they would run into a duplicate field selected error. This is because some field names from the accelerator were being referenced as internal fields when they should not be.

Field names in the accelerator and the product have been unified such that those in the former with the PJN prefix will be converted to their equivalent in the latter with the mvn namespace prefix. This means these legacy fields will be ignored in any future queries.

Spring '25 (V4.0.1)

Spring '25 (V4.0.4)

CC-4338

If a Salesforce org has a Care Plan (Case) record with over 200 open or closed Activity (Case) records, open activities may appear missing from the Additional Activities section in the Care Plan Timeline (pjnCarePlanTimeline) component on the Care Plan record page. For example, if a user creates a new activity for a care plan with more than 200 activities, the new open activity may not appear in the timeline, even if the user confirms that the new activity was saved successfully. This is because Salesforce limits subqueries to 200 child records.

Care plans and child cases are queried separately to avoid exceeding Salesforce's SOQL query limits.

Spring '25 (4.0.4)

Spring '25 (V4.0.7)

CC-4368

The Care Plan Highlighted Fields (pjnCarePlanHighlightedFields) component was not displaying the API field values configured in the Care Plan Field (mvn__PJN_Care_Plan_Field__mdt) metadata record because the query did not reference the Problem (HealthCloudGA__CarePlanProblem__c) field set.

Fields added to the Problem (HealthCloudGA__CarePlanProblem__c) field set are now automatically queried and displayed in the care plan user interface.

Spring '25 (v4.0.7)

Spring '25 (v4.0.8)