V1 release notes
This topic contains the release notes for V1 of Komodo Care Connect, including all patch and minor releases. The release notes are organized into these high-level sections:
New features – new features and functionalities released in the new version.
Updated features – updated features and functionalities released in the new version.
Defect fixes and maintenance – fixed defects and maintenance items within the new version.
Metadata changes – changes to the underlying data models, user permissions, or system configurations included within the new version.
Deprecated and deleted items – components of the product that have been deprecated, removed, or retired from the new version.
As this page is maintained and updated over time to ensure accurate and timely information, Komodo Health recommends referencing the release notes online rather than printing and referencing static versions of this page.
New features
The new release of Komodo Care Connect contains several new features whose functionalities are detailed below. Details about enablement and configuration are included within the product documentation.
V1.1.0 Automatic activity creation
Activity (Case) records can be automatically created upon a given event or trigger, such as 30 days before HIPAA consent expires on a care plan, via the mvn.PJN_CarePlanActivityService global Apex class that can also be called from a flow's action. For production documentation, reference Automatic activity creation.
Related work item: PJN-805
V1.1.0 Experian integration
Komodo Care Connect now integrates with Experian via the Experian Health API to evaluate a patient's Patient Assistance Program (PAP) eligibility. For all metadata object and field changes, reference Metadata changes below. For product documentation, reference Experian API.
Related work item: PJN-1160
V1.1.0 Data change request
Komodo Care Connect now provides a data change request (DCR) framework for users to monitor and track changes on any given object. This helps ensure that data and integrations with Komodo Care Connect relevant to external systems remain in sync as well as provide an audit trail for data changes on records satisfying certain criteria. The DCR framework uses new fields on the Data Change Request (mvn__PJN_Data_Change_Request__c) object as well as the new Data Change Request Line (mvn__PJN_Data_Change_Request_Line__c) object to track all data change request details. The DCR framework also uses the new Data Change Request Criteria (mvn__PJN_Data_Change_Request_Criteria__mdt) and Data Change Request Field (mvn__PJN_Data_Change_Request_Field__mdt) metadata types for users to define the criteria that determine which objects should trigger the DCR feature and which fields should be monitored for data changes. For product documentation, reference Data change requests (DCR).
Related work items: PJN-1543, PJN-1576
V1.2.0 New Prescription object
A new Prescription (mvn__PJN_Prescription__c) custom object has been created to replace the EHR Medication Prescription (HealthCloudGA__EhrMedicationPrescription__c) Health Cloud object. The EHR Medication Prescription object is part of Health Cloud's EHR data model and will be succeeded by the Clinical data model in Salesforce's Summer '23 release. (For more information, reference Salesforce's documentation on Electronic Health Records.) A custom object was used instead of the recommended Medication Request (MedicationRequest) Health Cloud object to ensure that Komodo Care Connect remains configurable and flexible for different patient services use cases, such as making sure a case manager of one program may not necessarily access the prescriptions of another program and that files can be attached to prescriptions.
Most fields from the EHR Medication Prescription object have been recreated on the new Prescription object exactly as they are. However, a few fields, such as those related to prescription quantity and dosage, have been updated from picklist and number fields to free text fields. For product documentation, reference Prescription.
Related work items: PJN-192, PJN-2076
V1.2.0 Event rollup
Events like therapy status updates can now roll up to their parent care plans via the new event rollup feature. The specific Event (mvn__PJN_Event__c) record type to roll up must be defined on the Event Rollup (mvn__PJN_Event_Rollup__mdt) custom metadata type while the source Event fields and the target Case fields must be defined on the Event Rollup Mapping (mvn__PJN_Event_Rollup_Mapping__mdt) custom metadata type. For product documentation, reference Event rollup.
Related work item: PJN-1354
Pharmacy status update
With the new event rollup feature, Komodo Care Connect now provides an out-of-the-box solution for processing status updates from pharmacies. Information can be captured in the new PJN_Pharmacy_Status_Update Event (mvn__PJN_Event__c) record type and then rolled up to pharmacy status and sub-status fields on the parent care plan. For product documentation, reference Pharmacies.
Related work items: PJN-1354, PJN-2412
V1.3.0 DocuSign integration
Komodo Care Connect now ships with both DocuSign's DocuSign Apps Launcher package and Komodo Health's DocuSign OneClick Toolkit package. These packages enable an integration with DocuSign to provide users with a one-click solution for requesting and capturing electronic signatures (eSignatures). The DocuSign OneClick Toolkit package is independent from the Komodo Care Connect product such that the DocuSign integration can be used with any object, including, but not limited to, the Consent (mvn__PJN_Contact_Point_Type_Consent__c) custom object to request and capture consent. For product documentation, reference DocuSign electronic signature and Capture consent with DocuSign.
Related work items: PJN-2645, PJN-2672, PJN-2701
V1.3.0 Enable/disable data change request framework
Admin users can now enable or disable the data change request (DCR) framework with the new Data Change Request Handler (PJN_DataChangeRequestHdlr) global Apex class. For product documentation, reference Data Change Request Handler and Data change requests (DCR).
Related work item: PJN-2664
V1.3.0 Mock data change request configuration for testing
Admin users can now mock the configuration of the data change request (DCR) framework in unit tests. Specifically, the new Data Change Request Criteria Selector (PJN_DataChangeRequestCriteriaSelector) and Data Change Request Field Selector (PJN_DataChangeRequestFieldSelector) global Apex classes allow developers to mock Data Change Request Criteria (mvn__PJN_Data_Change_Request_Criteria__mdt) and Data Change Request Field (mvn__PJN_Data_Change_Request_Field__mdt) metadata records, respectively. For product documentation, reference Mock DCR configuration for testing.
Related work item: PJN-2773
V1.3.0 Mapping Engine support of default business hours
The Mapping Engine has been updated to account for the default business hours. This means that for any source date to be mapped, the Mapping Engine will use both the Days to Add (mvn__PJN_Days_To_Add__c) field on the Mapping Date Formula (mvn__PJN_Mapping_Date_Formula__mdt) custom metadata type and the Default Business Hours record to calculate the final date to be stamped on a target field. Any day of the week that is not part of the Default Business Hours record is skipped in the final date calculation. For product documentation, reference Mapping Date Formula.
Related work items: PJN-2847, PJN-2939
Updated features
The new release of Komodo Care Connect also contains several improvements and optimizations to existing features and functionalities to better align with customer feedback and provide an enhanced user experience. Unless noted otherwise, all updated features are shipped "off" by default for existing customers and "on" by default for new customers.
V1.1.0 Configurable Account Search tiles
Account type tiles are now configured the same way as account type tabs. Previously, the tiles were limited to the four standard person account types provided out of the box. Now, the tiles are dynamic such that the existing tiles can be modified, new tiles can be added, and any action performed on a tile will be reflected on the corresponding tab as well. For product documentation, reference Configure account type filters.
Related work item: PJN-472
V1.1.0 Relationships and care team assignments
The building of relationships between accounts has been simplified and extended. The Case Field Configuration (mvn__PJN_Case_Field_Configuration__mdt) custom metadata type was previously the only metadata object available to configure both reciprocal relationships as well as care teams in care plans, which resulted in data redundancy in the metadata records and unscalability. The Case Field Configuration metadata type has now been simplified to primarily set accounts on a care plan to build a patient's care team while a new Relationship Role Configuration (mvn__PJN_Relationship_Role_Configuration__mdt) custom metadata type has been added to establish reciprocal relationships between accounts and contacts. This means that relationships in Komodo Care Connect have been extended from only Contact-Contact Relationship (HealthCloudGA__ContactContactRelation__c) records to include Account Contact Relationship (AccountContactRelation) records as well. For all metadata object and field changes, reference Metadata changes below. For product documentation, reference Care teams and Care Map.
Related work items: PJN-801, PJN-1221
V1.1.0 Overwrite trigger handlers for testing executions
Trigger handlers can now be overwritten for testing executions with the Trigger Handler Setting Query (mvn.PJN_TriggerHandlerSettingQuery) Apex class. Specifically, the setSettingsForObject method allows users to list which Trigger Handler Setting (mvn__PJN_Trigger_Handler_Setting__mdt) metadata records should run for a given object. For product documentation, reference Trigger Handler Setting Query.
Related work item: PJN-1367
V1.1.0 Account Search search order and configuration
The search order of Account Search has been updated to always search locally first within Komodo Care Connect and then iterate through other searches configured in the new Interface Handler (mvn__Interface_Handler__mdt) custom metadata type and add their results to the result set. This allows all account and related contact information to be solely managed in Komodo Care Connect. The mvn__PJN_Account_Search_Handler_Classes__c and mvn__PJN_Account_Search_Max_Results__c fields on the Global Setting (mvn__PJN_Global_Setting__mdt) custom metadata type have subsequently been deprecated.
To add external search integrations with Account Search, you can use the new Account Search Request (mvn.PJN_AccountSearchRequest) and Account Search Result (mvn.PJN_AccountSearchRequest) Apex classes to create a new search handler that implements the Account Search Interface (mvn.PJN_AccountSearchIntf). You can also configure the integration with the new Interface Handler (mvn__Interface_Handler__mdt) custom metadata type. For product documentation, reference Integrate with an external database.
Related work items: PJN-1416, PJN-1421, PJN-1426, PJN-1431, PJN-1474
V1.2.0 Improved content in Missing Information component
The Missing Information Config (mvn__PJN_Missing_Information_Config__mdt) custom metadata type has been updated to make the content that appears in the Missing Information (PJN_CaseMissingInformation) component be more informative for users. First, the existing Field Path (mvn__PJN_Field_Path__c) field has been extended to support nested relationships. Previously, it could only traverse lookup fields up to one level above the parent Care Plan (Case) record (e.g., Account.mvn__PJN_Primary_Address__c). Now, the Field Path field can traverse multiple lookup fields past the parent Care Plan record (e.g., Account.mvn__PJN_Primary_Address__r.mvn__PJN_Address_Line_1__c). Second, a new Display Text (mvn__PJN_Field_Label__c) field has been added for admin users to configure the text that specifies which fields on which records are missing required information. Previously, the Missing Information component only showed the object label and field label that was missing information (e.g., "Account: Gender"). Now, admin users can be more descriptive to help users more easily identify the specific record and field that needs to be populated (e.g., "Patient's Gender"). For product documentation, reference Missing information.
Related work items: PJN-1202, PJN-1205, PJN-2322
V1.2.0 Configure New Activity button
Admin users can now configure the New Activity button that appears for each stage on Care Plan (Case) record pages. On the Program Problem (mvn__PJN_Program_Problem__mdt) custom metadata type, use the Hide New Activity Button (mvn__PJN_Hide_New_Activity_Button__c) field to hide the button and use the New Activity Button Override (mvn__PJN_New_Activity_Button_Override__c) field to either relabel the button or configure the available Case record types that can be created in addition to or in place of the default PJN_Activity record type. For product documentation, reference Configure New Activity button.
Related work items: PJN-1344, PJN-1905
V1.3.0 Hide New Activity button
In addition to hiding the New Activity button for specific stages in a program, admin users can also hide the New Activity button for every stage in a care plan activity timeline (i.e., the PJN_CarePlanTimeline Aura component). For product documentation, reference Hide New Activity button.
Related work item: PJN-2838
V1.3.0 Hide New buttons in Medical History component
Similar to the New Activity button for care plan stages, admin users can now also hide the New buttons in the Medical History (pjnMedicalHistory) component. This prevents users from creating new records for all out-of-the-box and custom Medical History (mvn__PJN_Medical_History__c) record types, except for the Metric (PJN_Metric) record type. For product documentation, reference Display and configuration.
Related work item: PJN-2841
V1.3.0 Configure contact information parameters in Account Search
The Global Setting (mvn__PJN_Global_Setting__mdt) custom metadata type has been deprecated because it contained several extraneous fields that were not actively used as part of Komodo Care Connect and is superseded by the new Contact Info Record Types (mvn__PJN_Contact_Info_Record_Types__mdt) custom metadata type. Similar to the Global Setting custom metadata type, the Contact Info Record Types custom metadata type enables admin users to group Contact Information (mvn__PJN_Contact_Information__c) record types for Account Search to query when users enter an address, a phone number, a fax number, or an email in their search. For product documentation, reference Configure contact information search parameters.
Related work item: PJN-2685
V1.3.0 Updated layout of CarePlan record page
The CarePlan (PJN_CarePlan) Lightning record page that Komodo Care Connect provides out of the box has been updated to better organize the related lists on each care plan. Previously, the CarePlan record page contained a Related tab that consisted of all of the available related lists for users to view and manage records related to the Care Plan (Case) record. However, it was difficult for users to quickly navigate to each related list. Now, the CarePlan record page contains multiple tabs that group related lists together for users to easily find specific information. The Related tab has therefore been replaced with the Patient, Medical, Coverage, Fulfillment, and Events tabs. For product documentation, reference Tabs, components, and related lists.
Related work item: PJN-2065
Defect fixes and maintenance
Table 47, “Fixed items” details defects and maintenance items identified in V1 that were fixed in the V1.0.1 hotfix patch release, the V1.1.0, V1.2.0, and V1.3.0 minor releases, and the V1.3.1 patch release.
Work item | Description | New behavior | Version fixed |
|---|---|---|---|
PJN-801 | The Case Field Configuration ( | The Case Field Configuration metadata object is no longer used to configure reciprocal roles, so the three text fields used for this purpose have been removed. Reference Table 56, “Deprecated custom metadata type fields”. | V1.1.0 |
PJN-969 | The Coverage Investigation Item ( | The lookup fields to the Assistance Program and Prior Authorization objects on the Coverage Investigation Item object were extraneous and have been removed. | V1.0.1 |
PJN-970 | The Event ( | The text fields on the Event object were extraneous and have been removed. | V1.0.1 |
PJN-974 | When creating Contact Information ( | The "Business" picklist option has been removed from the Type field for | V1.0.1 |
PJN-976 | Non-admin users could not create a new record in the Medical History component without first selecting a Medical History ( |
| V1.0.1 |
PJN-977 | Within the Fulfillment Request ( | Any new Fulfillment Requests with the Materials Order ( | V1.0.1 |
PJN-978 | The New Care Plan button was listed in the Patient Navigation menu. | The New Care Plan button no longer appears in the Patient Navigation menu. | V1.0.1 |
PJN-980 | Notes created in Case records of | The titles of notes created in standalone Request ( | V1.0.1 |
PJN-981, PJN-1469, PJN-1861 | The layout for Event ( | A page layout and a compact layout have been created for the Therapy Access record type. They match the layouts of other Event record pages and contain relevant information such as the associated patient name and case number. | V1.2.0 |
PJN-982 | The page layouts for Medical History ( | The Related tab and right-hand column were extraneous and have been removed. All Medical History FlexiPages now span the full width of the screen. | V1.0.1 |
PJN-1002 | The Data Use Purpose table displayed the Legal Basis column, which was rarely used, and hid the names of care plans. | The Legal Basis Column was removed from the search view of the Data Use Purpose table. The example Data Use Purpose records were also updated to include care plan names. | V1.0.1 |
PJN-1018 | Physicians who were already on a care plan were not automatically added to a new prescription. | A care plan's existing physician is selected when a new prescription is created and edited. | V1.0.1 |
PJN-1061 | Stages in the progress bar of a care plan became too small when there were a large number of stages. This prevented users from identifying the individual stages and from clicking the stage, the start icon, the skip icon, or the delete icon without error. | A horizontal scroll has been added to the progress bar and a minimum width has been set on each stage. This allows the stages in the progress bar to remain readable and clickable regardless of how many there are. When a user opens the care plan, the progress bar also automatically scrolls to the current stage so that the user knows there are still open or planned stages left in the care plan. | V1.1.0 |
PJN-1062 | Users could not identify which fields were required when creating new or modifying existing Contact Information ( | The input form from the Contact Information component now reflects the Contact Information page layouts. Fields marked as required in the page layouts will appear as required when users create or edit records via the Contact Information component. | V1.0.1 |
PJN-1064 | When a user opens or refreshes the All Care Plans subtab for a patient account, the API name of the component ("mvn__PJN_All_Care_Plans") appeared in the browser tab instead of the display name ("All Care Plans"). | Extraneous header tags in the Visualforce page have been removed while a page title has been added. The browser tab now appears as "All Care Plans." | V1.1.0 |
PJN-1068 | Admin users ran into an error when saving new activities in care plans. | The | V1.0.1 |
PJN-1092 | The background design of the All Care Plans subtab always used Salesforce's Lightning Blue ( | The background design of the All Care Plans subtab has been set to a solid off-white color instead of using any theme or branding. | V1.1.0 |
PJN-1093 | When saving an Account Type Setting ( | A validation rule has been set on the Account Type Setting metadata type to ensure that if the Include in Create? ( | V1.1.0 |
PJN-1099 | The channel consent indicator icons on Contact Information ( | The indicator icons from Channel Consent ( NoteIf you select "Opt In," make sure you also enter the | V1.1.0 |
PJN-1112 | The Consent ( | The lookup field to the Individual object on the Consent object was extraneous and has been removed. Reference Table 64, “Deleted object fields”. | V1.1.0 |
PJN-1142 | Browsers such as the recommended Google Chrome are ending support for the
| The 1 Aura component has been converted into a Lightning Web Component, and all Lightning Web Components now use Salesforce's | V1.1.0 |
PJN-1215 | To search for a person account in Account Search, users had to enter the desired individual's last name before the individual's first name. This search field order is uncommon and therefore resulted in a poor user experience. | The search fields in Account Search have been rearranged via the corresponding Field Setting ( | V1.2.0 |
PJN-1221 | The Case Field Configuration ( | The two text fields on the Case Field Configuration metadata object were extraneous and have been deprecated. Reference Table 56, “Deprecated custom metadata type fields”. | V1.1.0 |
PJN-1312 | Admin users were unable to add certain fields to custom field sets. | All of the fields for the following objects can now be added to existing field sets:
| V1.2.0 |
PJN-1339 | If a custom user lookup field on a Care Plan ( | The OwnerId field of every Activity ( | V1.2.0 |
PJN-1370 | A script error was thrown when a new address was added to a physician account on a | The internal object that was causing the script error has been updated so that it is initialized before the new address is added to the physician account. | V1.1.0 |
PJN-1526 | The All Care Plans subtab threw an unexpected token error when the | The WarningCurrent customers should check that all existing All Care Plan Setting Field metadata records have a value in the | V1.1.0 |
PJN-1612, PJN-2114, PJN-2119 | Dependent picklist fields failed to work as expected in the Enrollment Wizard. If a parent (controlling) field and a child (dependent) field were both populated and saved in a single screen, the child field would not actually be saved in the record. Additionally, if a grandchild field existed, the grandchild field would remain disabled even if the parent and child fields were populated correctly, preventing users from making a selection. | Picklist dependency in the Enrollment Wizard has been fixed such that parent, child, and grandchild picklist fields open up for selection as appropriate and save user input as expected. | V1.2.0 |
PJN-1786 | Custom picklist fields on the Case object that are configured to appear in the Enrollment Wizard and whose default values are populated via the Mapping Engine caused the Enrollment Wizard to lag or freeze. This was because the creation of care plans occurred asynchronously such that the picklist field would appear in the Enrollment Wizard before the Mapping Engine could populate the default value. | The creation of care plans is now a synchronous process. There is no longer a delay in the population of custom Case picklist fields in the Enrollment Wizard via the Mapping Engine. | V1.2.0 |
PJN-1901 | File attachments in inbound emails did not appear in Account Search or the Enrollment Wizard when the emails were converted to Case records via the Email-to-Case functionality. The files only appeared in the Files related list on the | The file attachments from the inbound emails now appear in the Files related list as well as both Account Search and the Enrollment Wizard. | V1.2.0 |
PJN-1921 | Account Search threw an error when records of custom Business Account record types had a common word in their names. For example, if one record was named "metro infusion" while another record was named "infusion center" and a user searched "infusion" in Account Search, an error would appear. NoteThe names and search terms are case sensitive. | Account Search has been updated so that overlapping words in Business Account record names no longer prompt an error. | V1.2.0 |
PJN-1945 | After upgrading to Salesforce's Spring '23 release, users were no longer able to create Consent ( NoteThis issue was previously identified in KI-97. | The lookup filter criteria on the Patient field of the Consent object has been updated to properly reference the | V1.2.0 |
PJN-1960 | As part of Salesforce’s Spring ’23 release, the default display for the activity composer in Case record pages that is used to track contact attempts was changed from a tabbed view to a dynamic view. The update in the display made it confusing for users who want to log contact attempts that may or may not be phone calls. NoteThis issue was previously identified in KI-98. | The activity composer has been reverted from the new dynamic view to the original tabbed view, with all custom contact attempt labels appearing as expected. | V1.2.0 |
PJN-2091 | When users used the Patient Merge Tool, some records, such as the Assistance Program ( | Admin users still cannot manually allow reparenting on master-detail fields because the objects are part of the Komodo Care Connect managed package. However, the Allow Reparenting ( Additionally, a new | V1.2.0 |
PJN-2113 | As part of Salesforce’s Spring ’23 release, Lightning Web Security (LWS) is automatically enabled for Lightning Web Components and Aura components. Because of this update, users ran into a generic “Sorry to interrupt” error when selecting a patient in Account Search to enroll the patient into a care plan. NoteThis issue was previously identified in KI-99. | LWS has been turned off by default for Komodo Care Connect. Users can now select patient accounts in Account Search without errors. | V1.2.0 |
PJN-2582 | The Event ( | The quick actions have been removed from the Therapy Access page layout. | V1.3.0 |
PJN-2654 | The Parent Data Change Request ( | The Parent Data Change Request field has been removed from the Data Change Request object. | V1.3.0 |
PJN-3116 | When a non-admin user, such as a case manager, clicked the start ( | Clicking the icons on the stages in the care plan progress bar will start, skip, or delete the stages as expected. | V1.3.1 |
Metadata changes
The following subsections capture the changes against entities in key areas of Komodo Care Connect that have been introduced in the latest release. This list is not exhaustive, as it does not contain changes that are internal to the application and that are not exposed to customers for customization, extension, or integration. It also does not contain changes that pertain to the example programs configured by Komodo Care Connect.
Apex class changes are listed in the table below:
Work item | Apex class | Version added |
|---|---|---|
PJN-805 | mvn.PJN_CarePlanActivityService | V1.1.0 |
PJN-1367 | mvn.PJN_TriggerHandlerSettingQuery | V1.1.0 |
PJN-1416, PJN-1421, PJN-1426, PJN-1431, PJN-1474 | mvn.PJN_AccountSearchIntf mvn.PJN_AccountSearchRequest mvn.PJN_AccountSearchResult | V1.1.0 |
PJN-2664 | mvn.PJN_DataChangeRequestHdlr | V1.3.0 |
PJN-2773 | mvn.PJN_DataChangeRequestCriteriaSelector mvn.PJN_DataChangeRequestFieldSelector | V1.3.0 |
Aura component changes are listed in the table below:
Work item | Aura component | Modification explanation | Version modified |
|---|---|---|---|
PJN-2838 | PJN_CarePlanTimeline | The component now offers a Show New Activity Buttons checkbox that controls the visibility of all New Activity buttons in the component. | V1.3.0 |
Custom label changes are listed in the table below:
Work item | API name | Version added |
|---|---|---|
PJN-2645, PJN-2672, PJN-2701 | D1C_An_error_has_occurred_toolkit D1C_Envelope_Sent_toolkit D1C_Error_Sending_Envelope_toolkit D1C_Locating_DocuSign_Template_toolkit D1C_Searching_For_Config_toolkit D1C_Sending_Envelope_toolkit D1C_Unable_to_find_templates_toolkit D1C_Unable_to_Locate_Setting_toolkit D1C_Unable_to_Locate_Template_toolkit D1C_Unable_to_query_record_toolkit | V1.3.0 |
Custom metadata type changes are listed in these tables below:
Work item | Custom metadata type | Version added |
|---|---|---|
PJN-801, PJN-1221 | mvn__PJN_Relationship_Role_Configuration__mdt | V1.1.0 |
PJN-1160 | mvn__PJN_Assistance_Prog_Eligibility_Config__mdt | V1.1.0 |
PJN-1354 | mvn__PJN_Event_Rollup__mdt mvn__PJN_Event_Rollup_Mapping__mdt | V1.2.0 |
PJN-1416, PJN-1421, PJN-1426, PJN-1431, PJN-1474 | mvn__Interface_Handler__mdt | V1.1.0 |
PJN-1543, PJN-1576 | mvn__PJN_Data_Change_Request_Criteria__mdt mvn__PJN_Data_Change_Request_Field__mdt | V1.1.0 |
PJN-2645, PJN-2672, PJN-2701 | mvn__DocuSign_One_Click_Recipient__mdt mvn__DocuSign_One_Click_Setting__mdt mvn__DocuSign_OneClick_Envelope_Update__mdt | V1.3.0 |
PJN-2685 | mvn__PJN_Contact_Info_Record_Types__mdt | V1.3.0 |
Work item | Custom metadata type | Field | Version added |
|---|---|---|---|
PJN-472 | mvn__PJN_Account_Type_Setting__mdt | mvn__PJN_Acc_Relationship_API_Name_For_Case__c mvn__PJN_Logo_Path__c | V1.1.0 |
PJN-1205 | mvn__PJN_Missing_Information_Config__mdt | mvn__PJN_Field_Label__c | V1.2.0 |
PJN-1344 | mvn__PJN_Program_Problem__mdt | mvn__PJN_New_Activity_Button_Override__c | V1.2.0 |
PJN-1905 | mvn__PJN_Program_Problem__mdt | mvn__PJN_Hide_New_Activity_Button__c | V1.2.0 |
Work item | Custom metadata type | Metadata record name | Version added |
|---|---|---|---|
PJN-1354 | mvn__PJN_Event_Rollup__mdt | MVN_Pharmacy_Status_Update MVN_Therapy_Status_Update | V1.2.0 |
mvn__PJN_Event_Rollup_Mapping__mdt | MVN_New_Pharmacy_Status MVN_New_Pharmacy_Sub_Status MVN_New_Therapy_Status MVN_New_Therapy_Sub_Status | ||
PJN-2091 | mvn__PJN_Merge_Tool_Setting__mdt | PJN_Coverage_Investigation | V1.2.0 |
PJN-2377 | mvn__PJN_Care_Plan_Field_Mapping__mdt | PJN_Prescription | V1.2.0 |
PJN-2685 | mvn__PJN_Contact_Info_Record_Types__mdt | PJN_Contact_Info_Address PJN_Contact_Info_Email PJN_Contact_Info_Fax PJN_Contact_Info_Phone | V1.3.0 |
Work item | Custom metadata type | Metadata record name | Modification explanation | Version modified |
|---|---|---|---|---|
PJN-192 | mvn__PJN_Care_Plan_Lookup_Mapping__mdt | PJN_Set_Primary_Prescription | The SObject API Name ( | V1.2.0 |
mvn__PJN_File_Rollup_Setting__mdt | PJN_Prescription | The sObject API Name ( | ||
mvn__PJN_Mapping__mdt | PJN_Set_Primary_Prescription | The Source Object API Name ( | ||
mvn__PJN_Mapping_Job__mdt | PJN_Prescription_Creation | The Target Object API Name ( | ||
mvn__PJN_Merge_Tool_Setting__mdt | PJN_Prescription | The Child SObject API Name ( | ||
mvn__PJN_Trigger_Handler_Setting__mdt | PJN_After_Insert_Prescription_Mapping PJN_After_Update_Prescription_Mapping PJN_Before_Insert_Prescription_Care_Plan PJN_Before_Insert_Prescription_Mapping PJN_Before_Update_Prescription_Mapping | The SObject API Name ( | ||
PJN-2076 | mvn__PJN_Mapping_Field__mdt | PJN_Set_Primary_Prescription | The Target Field API Name ( | V1.2.0 |
Work item | Custom metadata type | Description | Version deprecated |
|---|---|---|---|
PJN-2685 | mvn__PJN_Global_Setting__mdt | The Global Setting ( | V1.3.0 |
Work item | Custom metadata type | Field | Description | Version deprecated |
|---|---|---|---|---|
PJN-801, PJN-1221 | mvn__PJN_Case_Field_Configuration__mdt | mvn__PJN_Case_Team_Inverse_Role_Mapping__c | The name of the reciprocal role. | V1.1.0 |
mvn__PJN_Delete_Care_Team_Role_on_change__c | When | |||
mvn__PJN_Reciprocal_Inverse_Role__c | The care team role that the selected Account record type has a relationship with. | |||
mvn__PJN_Reciprocal_Inverse_Role_Case_Field__c | The API name of the field on the Case object that the reciprocal role maps to. | |||
mvn__PJN_Reciprocal_Role_Case_Field__c | The API name of the field on the Case object that the selected Account record type maps to. | |||
PJN-1416, PJN-1421, PJN-1426, PJN-1431, PJN-1474 | mvn__PJN_Global_Setting__mdt | mvn__PJN_Account_Search_Handler_Classes__c | The list of classes used in Account Search. Each class must implement the If there are duplicate results, only the first result appears. For example, a value of NoteOut of the box, Komodo Care Connect only ships with the If custom search handlers are needed to facilitate additional account searches, make sure they implement the | V1.1.0 |
mvn__PJN_Account_Search_Max_Results__c | The maximum number of search results returned by Account Search. This cannot exceed the SOSL limit of 200. |
Work item | Custom metadata type | Metadata record name | Version deleted |
|---|---|---|---|
PJN-192 | mvn__PJN_Care_Plan_Field_Mapping__mdt | PJN_EhrMedicationPrescription | V1.2.0 |
PJN-1786 | mvn__PJN_Trigger_Handler_Setting__mdt | PJN_After_Insert_Program_Event_Sub | V1.2.0 |
Lightning component changes are listed in the table below:
Work item | Lightning component | Version added |
|---|---|---|
PJN-2645, PJN-2672, PJN-2701 | docuSignOneClickQuickAction | V1.3.0 |
Work item | Lightning component | Modification explanation | Version modified |
|---|---|---|---|
PJN-1612, PJN-2114, PJN-2119 | pjnEnrollmentWizardInputForm | The component has been updated to resolve issues with picklist dependencies in the Enrollment Wizard. | V1.2.0 |
PJN-2841 | pjnMedicalHistory | The component has been updated to include a new Hide New Medical Record Buttons attribute. | V1.3.0 |
Object changes are listed in these tables below:
Work item | Object | Version added |
|---|---|---|
PJN-192 | mvn__PJN_Prescription__c | V1.2.0 |
PJN-1543, PJN-1576 | mvn__PJN_Data_Change_Request_Line__c | V1.1.0 |
Work item | Object | Field | Version added |
|---|---|---|---|
PJN-1339 | Case | mvn__PJN_Alternative_Activity_Owner__c | V1.2.0 |
PJN-1354 | Case | mvn__PJN_Pharmacy_Status__c mvn__PJN_Pharmacy_Status_Formula__c mvn__PJN_Pharmacy_Sub_Status__c | V1.2.0 |
mvn__PJN_Event__c | mvn__PJN_New_Pharmacy_Status__c mvn__PJN_New_Pharmacy_Sub_Status__c | ||
PJN-1543, PJN-1576 | mvn__PJN_Data_Change_Request__c | mvn__PJN_Account__c mvn__PJN_Contact_Information__c mvn__PJN_Country__c mvn__PJN_External_Id__c mvn__PJN_Parent_Data_Change_Request__c | V1.1.0 |
PJN-2076 | Case | mvn__PJN_Patient_Primary_Prescription__c | V1.2.0 |
Work item | Object | Record type | Version added |
|---|---|---|---|
PJN-1354 | mvn__PJN_Event__c | PJN_Pharmacy_Status_Update | V1.2.0 |
Work item | Object | Field | Modification explanation | Version modified |
|---|---|---|---|---|
PJN-2091 | mvn__PJN_Assistance_Program__c | mvn__PJN_Care_Plan__c | The Allow Reparenting ( | V2 |
mvn__PJN_Channel_Consent__c | mvn__PJN_Contact_Information__c | |||
mvn__PJN_Coverage_Benefit__c | mvn__PJN_Member_Plan__c | |||
mvn__PJN_Coverage_Investigation__c | mvn__PJN_Care_Plan__c | |||
mvn__PJN_Coverage_Investigation_Item__c | mvn__PJN_Coverage_Investigation__c | |||
mvn__PJN_Data_Change_Request_Line__c | mvn__PJN_Data_Change_Request__c | |||
mvn__PJN_Event_Log__c | mvn__PJN_Event__c | |||
mvn__PJN_License__c | mvn__PJN_Account__c | |||
mvn__PJN_Metric_Type__c | mvn__PJN_Metric_Group__c | |||
mvn__PJN_Metric_Type_Option__c | mvn__PJN_Metric_Type__c | |||
mvn__PJN_Prior_Authorization__c | mvn__PJN_Member_Plan__c | |||
mvn__PJN_Program_Metric_Type__c | mvn__PJN_Care_Program__c mvn__PJN_Metric_Type__c |
Work item | Object | Field | Description | Version deleted |
|---|---|---|---|---|
PJN-969 | mvn__PJN_Coverage_Investigation_Item__c | mvn__PJN_Assistance_Program__c | The related Assistance Program ( | V1.0.1 |
mvn__PJN_Prior_Authorization__c | The related Prior Authorization ( | |||
PJN-970 | mvn__PJN_Event__c | mvn__PJN_Patient_Email_Address__c | The patient email address used for inbound data mapping. | V1.0.1 |
mvn__PJN_Request_Date__c | The request date used for inbound data mapping. | |||
PJN-1112 | mvn__PJN_Contact_Point_Type_Consent__c | mvn__PJN_Party__c | The related Individual record. | V1.1.0 |
PJN-2076 | Case | mvn__PJN_Primary_Prescription__c | The related EHR Medication Prescription ( | V1.2.0 |
PJN-2654 | mvn__PJN_Data_Change_Request__c | mvn__PJN_Parent_Data_Change_Request__c | The parent Data Change Request record. This is only used if there are multiple data change requests being created in a single step. | V1.3.0 |
Work item | Object | Description | Version deprecated |
|---|---|---|---|
PJN-192 | HealthCloudGA__EhrMedicationPrescription__c | The Prescription ( | V1.2.0 |
Permission changes are listed in the table below:
Work item | Permission set | Version added |
|---|---|---|
PJN-1543, PJN-1576 | PJN_Data_Change_Request | V1.1.0 |
PJN-2645, PJN-2672, PJN-2701 | DocuSign_OneClick_Permissions | V1.3.0 |
Quick action changes are listed in the table below:
Work item | Object | Quick action | Version added |
|---|---|---|---|
PJN-1160 | mvn__PJN_Assistance_Program__c | PJN_Evaluate_PAP_Eligibility | V1.1.0 |
Deprecated and deleted items
The following entities have either been deprecated or deleted from the latest release of Komodo Care Connect and will no longer be available or supported in future releases.
Work item | Custom metadata type | Description | Version deprecated |
|---|---|---|---|
PJN-2685 | mvn__PJN_Global_Setting__mdt | The Global Setting ( | V1.3.0 |
Work item | Custom metadata type | Field | Description | Version deprecated |
|---|---|---|---|---|
PJN-801, PJN-1221 | mvn__PJN_Case_Field_Configuration__mdt | mvn__PJN_Case_Team_Inverse_Role_Mapping__c | The name of the reciprocal role. | V1.1.0 |
mvn__PJN_Delete_Care_Team_Role_on_change__c | When | |||
mvn__PJN_Reciprocal_Inverse_Role__c | The care team role that the selected Account record type has a relationship with. | |||
mvn__PJN_Reciprocal_Inverse_Role_Case_Field__c | The API name of the field on the Case object that the reciprocal role maps to. | |||
mvn__PJN_Reciprocal_Role_Case_Field__c | The API name of the field on the Case object that the selected Account record type maps to. | |||
PJN-1416, PJN-1421, PJN-1426, PJN-1431, PJN-1474 | mvn__PJN_Global_Setting__mdt | mvn__PJN_Account_Search_Handler_Classes__c | The list of classes used in Account Search. Each class must implement the If there are duplicate results, only the first result appears. For example, a value of NoteOut of the box, Komodo Care Connect only ships with the If custom search handlers are needed to facilitate additional account searches, make sure they implement the | V1.1.0 |
mvn__PJN_Account_Search_Max_Results__c | The maximum number of search results returned by Account Search. This cannot exceed the SOSL limit of 200. |
Work item | Custom metadata type | Metadata record name | Version deleted |
|---|---|---|---|
PJN-192 | mvn__PJN_Care_Plan_Field_Mapping__mdt | PJN_EhrMedicationPrescription | V1.2.0 |
PJN-1786 | mvn__PJN_Trigger_Handler_Setting__mdt | PJN_After_Insert_Program_Event_Sub | V1.2.0 |
Work item | Object | Description | Version deprecated |
|---|---|---|---|
PJN-192 | HealthCloudGA__EhrMedicationPrescription__c | The Prescription ( | V1.2.0 |
Work item | Object | Field | Description | Version deleted |
|---|---|---|---|---|
PJN-969 | mvn__PJN_Coverage_Investigation_Item__c | mvn__PJN_Assistance_Program__c | The related Assistance Program ( | V1.0.1 |
mvn__PJN_Prior_Authorization__c | The related Prior Authorization ( | |||
PJN-970 | mvn__PJN_Event__c | mvn__PJN_Patient_Email_Address__c | The patient email address used for inbound data mapping. | V1.0.1 |
mvn__PJN_Request_Date__c | The request date used for inbound data mapping. | |||
PJN-1112 | mvn__PJN_Contact_Point_Type_Consent__c | mvn__PJN_Party__c | The related Individual record. | V1.1.0 |
PJN-2076 | Case | mvn__PJN_Primary_Prescription__c | The related EHR Medication Prescription ( | V1.2.0 |
PJN-2654 | mvn__PJN_Data_Change_Request__c | mvn__PJN_Parent_Data_Change_Request__c | The parent Data Change Request record. This is only used if there are multiple data change requests being created in a single step. | V1.3.0 |