Skip to main content

Hotfixes

This page lists the defects that were identified in Komodo Care Connect and fixed with hotfix patches.

Komodo Care Connect Spring '25

Table 101, “Hotfix items” details defects identified in Komodo Care Connect Spring '25 that were fixed via a hotfix patch. You may click the links in the "Version fixed" column to install the hotfix with the Install Service.

Table 101. Hotfix items

Work item	Description	New behavior	Version affected	Version fixed
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. Note This issue was previously identified in KI-139.	Relationships created from custom configurations via the Case field Configuration and Relationship Role Configuration custom metadata types will have the correct roles. Additionally, Komodo 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)