Release notes

CC-3712

Some custom metadata types did not have page layouts that contain all of the key fields that users may need to effectively and efficiently use Care Connect out of the box. This meant that admins needed to spend more time creating and configuring the page layouts for effective use of the product.

The default Case Field Configuration Layout for the Case Field Configuration (mvn__PJN_Case_Field_Configuration__mdt) custom metadata type has been updated to include the Delete Care Team Role On (mvn__PJN_Delete_Care_Team_Role_on_change__c) field while the default Mapping Label Layout for the Mapping Label mvn__PJN_Mapping_Label__mdt) custom metadata type has been updated to include the Target Field Type (mvn__PJN_Target_Field_Type__c) field. Additionally, the new Care Plan Field Layout is available as the default page layout for the Care Plan Field (mvn__PJN_Care_Plan_Field__mdt) custom metadata type.

CC-3807

When a care plan did not have an active, or Open, stage to be the default selected stage and a user opened the CarePlan (PJN_CarePlan) record page, the Care Plan Problem Info (pjnCarePlanProblemInfo) component appeared as a thin white rectangle. This was because the highlighted and key fields inside the Care Plan Problem Info component only rendered when there was a selected stage. If a user clicked on a stage in the care plan progress bar so that it became a selected stage, the Care Plan Problem Info component rendered properly again.

If a care plan does not have an active or selected stage, the Care Plan Problem Info component renders with the key fields for the care plan and no highlighted fields for any specific stage. This update applies to the Care Plan Problem Info component on both the CarePlan record page and the All Care Plans tab.

CC-3843

If a Data Change Request (mvn__PJN_Data_Change_Request__c) record is created for a patient merge request and the Patient 1 (mvn__PJN_Patient_1__c) and Patient 2 (mvn__PJN_Patient_2__c) fields look up to the same Account record, the Patient Merge Tool will throw a "List index out of bounds" error when a user clicks Finish in the final screen of the wizard. This is because the Patient Merge Tool cannot merge two patients that are actually the same account.

The Prevent Duplicate Patient Assignment (PJN_Prevent_Duplicate_Patient_Assignment) validation rule will be added to the Data Change Request (DCR) object to ensure that the Account records on the Patient 1 and Patient 2 fields are different. If a user inputs the same Account record on both fields, the DCR object will throw a "Patient 1 and Patient 2 cannot be the same" error and prevent the DCR record from being created. This is a more user-friendly error message and will prevent users from trying to use an invalid DCR to start and submit a merge request with the Patient Merge Tool.

CC-3931

When a user clicked Create Care Plan in the Enrollment Wizard and then clicked either Cancel or X to close out of the wizard without completing the entire enrollment form, the care plan would be created but the Care Plan (Case) record did not open automatically.

If a user exits out of the Enrollment Wizard after creating a care plan without completing the enrollment form, the user is taken to the subtab with the newly created Care Plan record automatically.

CC-3941

When a record form in the Enrollment Wizard did not have any free text fields, the fields and field labels in the record form would not span the entire width of the Enrollment Wizard. As a result, some field labels wrapped to the next line and even cut off some words, making it difficult for users to read. This issue worsened when the display density setting for the Salesforce org was set to compact.

The record forms in the Enrollment Wizard will always span the entire width, even if there are no free text fields.

CC-4028

When new alignment data was uploaded for Zip To Team and Zip To Team was re-run for multiple programs, a "List index out of bounds" error would be thrown. This is because the unique keys that Zip To Team generated to ensure that each zip code is only used for a single program did not always map one-to-one with the programs.

The Zip To Team functionality has been refactored to ensure proper mappings between the keys and the programs. This also simplifies, optimizes, and streamlines how Care Connect assigns case managers to care plans and patients.

CC-4087

When the Role (mvn__PJN_Role__c) value on an existing Relationship Role Configuration (mvn__PJN_Relationship_Role_Configuration__mdt) metadata record was updated or when a new Relationship Role Configuration metadata record was created for the same business account and person account (i.e., contact), Care Connect tried to create a new Account Contact Relationship (AccountContactRelation) record for the new or additional roles. However, because Salesforce only allows one Account Contact Relationship record to be created between each account and contact, Salesforce identified the new record as a duplicate of the existing record and threw an error message.

An error was thrown because Salesforce uses the combination of AccountId and ContactId values to determine if an Account Contact Relationship record is unique whereas Care Connect used the combination of AccountId, ContactId, and Role values to determine if an Account Contact Relationship record is unique. To align with Salesforce's criteria, Care Connect no longer uses the Role value to check for duplicate Account Contact Relationship records. If the Role value on an existing Relationship Role Configuration metadata record is updated or if multiple Relationship Role Configuration metadata records are created for the same account and contact, the Roles field on the corresponding Account Contact Relationship record updates to append the new or additional roles.

CC-4190

When a user clicked Review Enrollment on a Request (Case) record to open the Enrollment Wizard for an existing care plan and then clicked either Cancel or X to close out of the wizard without completing the entire enrollment form, the user was always taken to the right-most subtab. This could be confusing for the user because the right-most subtab may not always be related to the request, care plan, or enrollment.

If a user opens an existing enrollment form and then exits out of the Enrollment Wizard without completing the enrollment form, the user is taken to the source Request record subtab from which they opened the Enrollment Wizard.

CC-4248

When an integration user passes a JSON payload to the eRX API (PJN_ErxApi) to submit an electronic prescription enrollment (eRX) request, the integration user may receive an "Insert failed... CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY" error message. This is because Salesforce's assignment rules changes the owner ID on the Care Plan (Case) record throughout the processing of the eRX API call and the creation of the care plan.

A new Trigger Handler Setting (mvn__PJN_Trigger_Handler_Setting__mdt) metadata record, PJN_Before_Update_Case_Revert_Case_Owner, is available to call the new non-global PJN_CaseRevertCaseOwner Apex class and revert any changes that Salesforce's assignment rules make to care plan owners.

CC-4286

When a user tried to edit a Contact Information (mvn__PJN_Contact_Information__c) record from the Contact Information (PJN_ContactInformation) component, the Set as Primary (mvn__PJN_Set_as_Primary__c) field in the edit modal sometimes appeared checked (i.e., set to true) and did not reflect the actual value on the Contact Information record.

The edit modal from the Contact Information component has been updated to always show the actual values on the selected Contact Information record instead of the default values on the Contact Information fields.

CC-4290

The Apex classes and triggers in Care Connect were all on older and different versions of Salesforce's API.

All of the Apex classes and triggers in Care Connect have been updated to Salesforce's latest API version, Version 64.0, for the latest platform features, performance improvements, and security enhancements.