Custom metadata
This reference page lists the custom metadata objects that help define the Komodo Care Connect framework and configure product behavior.
The Account Search Additional Filters (mvn__PJN_Account_Search_Additional_Filters__mdt
) custom metadata type defines the rules, or filters, that determine which Account and/or Contact Information (mvn__PJN_Contact_Information__c
) records are returned as search results by Account Search.
Field label | API name | Data type | Description |
---|---|---|---|
Rule | mvn__PJN_Rule__c | Long Text Area(131072) | The JSON string representing the rule or set of rules that determines if a record will be returned in Account Search. If the rule evaluates to NoteFor guidelines on how to write the JSON criteria, reference Criteria definition. |
The Account Type Setting (mvn__PJN_Account_Type_Setting__mdt
) custom metadata type defines the account types under Person Accounts and Business Accounts that users can use as filters in Account Search.
Field label | API name | Data type | Description |
---|---|---|---|
Acc Lookup Field API Name For Case | mvn__PJN_Acc_Lookup_Field_API_Name_For_Case__c | Text(64) | The API name of the lookup field on the Case record that will store the value of an Account Search selection of this account type when Account Search is launched from a Request Case record. |
Account Record Type | mvn__PJN_Account_Record_Type__c | Text(57) | The API name of the associated Account record type. |
Account Search Order | mvn__PJN_Account_Search_Order__c | Number(2, 0) | The order that the account type appears in the search filters. |
Acc Relationship API Name For Case | mvn__PJN_Acc_Relationship_API_Name_For_Case__c | Text(64) | The API name of the relationship between the account and the Care Plan ( |
Include in Create? | mvn__PJN_Include_in_Create__c | Checkbox | When set to |
Include in Search? | mvn__PJN_Include_in_Search__c | Checkbox | When set to |
Is Person Record Type? | mvn__PJN_Is_Person_Record_Type__c | Checkbox | When set to |
Logo Path | mvn__PJN_Logo_Path__c | URL | The path to the Salesforce icon that will be used as the account type logo in Account Search. For example, NoteThe |
Supplemental Account Search Record Types | mvn__PJN_Supplemental_Acct_Search_Rec_Types__c | Text(255) | A comma-separated list of the API names of other Account record types that should be searched when this record type is selected in Account Search. |
The All Care Plan Setting (mvn__PJN_All_Care_Plan_Setting__mdt
) custom metadata type defines the information displayed in the All Care Plans subtab.
Field label | API name | Data type | Description |
---|---|---|---|
Is Path Expandable | mvn__PJN_Is_Path_Expandable__c | Checkbox | Indicates whether the path is expandable. |
Program | mvn__PJN_Program__c | Metadata Relationship(Program) | The related Program ( |
Subtitle Field API Name | mvn__PJN_Subtitle_Field_API_Name__c | Text(255) | The API name of the field on the Case record that appears as the subtitle. |
Title Field API Name | mvn__PJN_Title_Field_API_Name__c | Text(255) | The API name of the field on the Case record that appears as the title. |
The All Care Plan Setting Field (mvn__PJN_All_Care_Plan_Setting_Field__mdt
) custom metadata type defines which fields will be displayed in the All Care Plans subtab and the order in which they appear.
Field label | API name | Data type | Description |
---|---|---|---|
All Care Plan Setting | mvn__PJN_All_Care_Plan_Setting__c | Metadata Relationship(All Care Plan Setting) | The related All Care Plan Setting ( |
Field API Name | mvn__PJN_Field_API_Name__c | Text(255) | The API name of the field that provides the value to display. |
Field Label | mvn__PJN_Field_Label__c | Text(255) | The label that appears when rendered. |
Link Record Id Field API Name | mvn__PJN_Link_Record_Id_Field_API_Name__c | Text(255) | The API name of the field which provides the lookup, if the field represents a lookup to another record. |
Order | mvn__PJN_Order__c | Number(3, 0) | The order in which the field will appear. |
The Assistance Program Eligibility Config (mvn__PJN_Assistance_Prog_Eligibility_Config__mdt
) custom metadata type configures the functionality to connect to an external vendor and assess a patient's Patient Assistance Program (PAP) eligibility.
Warning
Only one Assistance Program Eligibility Config (mvn__PJN_Assistance_Prog_Eligibility_Config__mdt
) metadata record can exist, and it must have a record name of PJN_Main_Configuration
.
Field label | API name | Data type | Description |
---|---|---|---|
Clearing House Class | mvn__PJN_Clearing_House_Class__c | Text(50) | The Apex class that assesses PAP eligibility. The default value of |
The Care Plan Field (mvn__PJN_Care_Plan_Field__mdt
) custom metadata type defines the guidance information that appears on the right side of and under the stage progress section of a Care Plan (Case
) record page.
Field label | API name | Data type | Description |
---|---|---|---|
CarePlan Path Coaching Setting | mvn__PJN_CarePlan_Path_Coaching_Setting__c | Metadata Relationship(CarePlan Path Coaching Setting) | The related CarePlan Path Coaching Setting ( |
Field API Name | mvn__PJN_Field_API_Name__c | Text(80) | The API name of the field on the Care Plan ( |
Field Label | mvn__PJN_Field_Label__c | Text(80) | The name of the guidance information that appears to users. |
Icon Name | mvn__PJN_Icon_Name__c | Text(50) | The name of the Salesforce Lightning Design System icon that appears alongside the guidance information. The format is |
Icon Size | mvn__PJN_Icon_Size__c | Picklist | The size of the Salesforce Lightning Design System icon that appears alongside the guidance information. Possible values are:
|
Order | mvn__PJN_Order__c | Number(2, 0) | The order that the value defined in the |
Program | mvn__PJN_Program__c | Metadata Relationship(Program) | The related Program ( |
The Care Plan Field Mapping (mvn_PJN_Care_Plan_Field_Mapping__mdt
) custom metadata type defines the mapping for Care Plan Field (mvn__PJN_Care_Plan_Field__mdt
) metadata records.
Field label | API names | Data type | Description |
---|---|---|---|
Active | mvn__PJN_Active__c | Checkbox | When |
Care Plan Lookup API Name | mvn__PJN_Care_Plan_Lookup_API_Name__c | Text(255) | The API name of the lookup field on the sObject that relates to the care plan field. |
Id API Name | mvn__PJN_Id_API_Name__c | Text(255) | The Creation UUID value of the sObject. |
Mapping Job Name | mvn__PJN_Mapping_Job_Name__c | Text(255) | The API name of the parent mapping job. |
SObject API Name | mvn__PJN_SObject_API_Name__c | Text(255) (Unique Case Sensitive) | The API name of the sObject that is related to the care plan field. |
The Care Plan Lookup Mapping (mvn__PJN_Care_Plan_Lookup_Mapping__mdt
) custom metadata type defines the mapping onto a Care Plan (Case
) record during record creation or insertion, including details such as the source object from which the data is pulled and the fields on the Care Plan record to which the data is mapped.
Field label | API name | Data type | Description |
---|---|---|---|
Active | mvn__PJN_Active__c | Checkbox | When |
Care Plan Lookup API Name | mvn__PJN_Care_Plan_Lookup_API_Name__c | Text(255) | The API name of the lookup field on the sObject that relates to the Care Plan ( |
Id API Name | mvn__PJN_Id_API_Name__c | Text(255) | The Creation UUID value of the sObject. |
Indicator API Name | mvn__PJN_Indicator_API_Name__c | Text(255) | The API name of the field on the sObject that indicates if data should be mapped to the care plan. |
Indicator To Update API Name | mvn__PJN_Indicator_To_Update_API_Name__c | Text(255) | The API name of the checkbox field on the sObject that must be updated to |
Mapping Job Name | mvn__PJN_Mapping_Job_Name__c | Text(255) | The API name of the parent mapping job. |
SObject API Name | mvn__PJN_SObject_API_Name__c | Text(255) | The API name of the sObject that is related to the Care Plan ( |
The Care Plan Timeline Case (mvn_PJN_Care_Plan_Timeline_Case__mdt
) custom metadata type defines the icons that appear in the care plan activity timeline for the different activity types or statuses of a given program.
Field label | API name | Data type | Description |
---|---|---|---|
Activity Type | mvn__PJN_Activity_Type__c | Text(255) | The API name of the associated activity type. |
Icon Name | mvn__PJN_Icon_Name__c | Text(50) | The name of the Salesforce Lightning Design System icon that appears alongside the guidance information. The format is |
Program | mvn__PJN_Program__c | Metadata Relationship(Program) | The related Program ( |
The Care Plan Timeline Case Field (mvn_PJN_Care_Plan__Timeline_Case_Field__mdt
) custom metadata type defines the fields that appear in the care plan activity timeline for each Care Plan Timeline Case (mvn__PJN_Care_Plan_Timeline_Case__mdt
) metadata record based on the activity type or status.
Field label | API name | Data type | Description |
---|---|---|---|
Care Plan Timeline Case | mvn__PJN_Care_Plan_Timeline_Case__c | Metadata Relationship(Care Plan Timeline Case) | The parent Care Plan Timeline Case ( |
Field API Name | mvn__PJN_Field_API_Name__c | Text(80) | The API name of the field on the Care Plan Timeline Case metadata record where the information is sourced from. |
Field Label | mvn__PJN_Field_Label__c | Text(80) | The name of the guidance information that appears to users. |
Order | mvn__PJN_Order__c | Number(2, 0) | The order that the field is displayed in the care plan activity timeline. |
The CarePlan Path Coaching Setting (mvn__PJN_CarePlan_Path_Coaching_Setting__mdt
) custom metadata type manages the guidance information and key fields for a given program problem (stage) and care plan.
Field label | API name | Data type | Description |
---|---|---|---|
Component Name | mvn__PJN_Component_Name__c | Text(255) | The type of component. Possible values are:
|
Mode | mvn__PJN_Mode__c | Picklist | The class that is added to the container. Possible values are:
NoteIf the same mode is selected for multiple CarePlan Path Coaching Setting records, then the key fields and guidance information will render alphabetically by name. |
Program Problem | mvn__PJN_Program_Problem__c | Metadata Relationship(Program Problem) | The related Program Problem ( |
The CarePlan Path Keys Setting (mvn__PJN_CarePlan_Path_Keys_Setting__mdt
) custom metadata type defines the key fields that appear in the care plan progress section of a Care Plan (Case
) record page for a program problem (stage).
Field label | API name | Data type | Description |
---|---|---|---|
CarePlan Path Coaching Setting | mvn__PJN_CarePlan_Path_Coaching_Setting__c | Metadata Relationship(CarePlan Path Coaching Setting) | The related CarePlan Path Coaching Setting ( |
Columns | mvn__PJN_Columns__c | Number(1, 0) | The number of columns that the Care Plan ( |
Fields | mvn__PJN_Fields__c | Long Text Area(1000) | The API names of the fields on the Care Plan ( |
The Case Field Configuration (mvn__PJN_Case_Field_Configuration__mdt
) custom metadata type drives the PJN_CaseTeamMemberHdlr
trigger handler to add care team members to care plans. It does so by identifying the field on the Care Plan (Case
) object that a selected Account record type in Account Search maps to. The Case Field Configuration metadata type also enables the creation of reciprocal relationships, which is managed by the Relationship Role Configuration (mvn__PJN_Relationship_Role_Configuration__mdt
) custom metadata type.
Field label | API name | Data type | Description |
---|---|---|---|
Account Record Type | mvn__PJN_Account_Record_Type__c | Text(100) | The selected Account record type in Account Search. |
Case Field API Name | mvn__PJN_Case_Field_API_Name__c | Text(43) | The API name of the lookup field on the Care Plan ( |
Case Team Inverse Role Mapping | mvn__PJN_Case_Team_Inverse_Role_Mapping__c | Text(100) | The name of the reciprocal role. WarningThis field has been deprecated as of V1.1.0 and is only available in V1.0.1 and below. |
Case Team Role Mapping | mvn__PJN_Case_Team_Role_Mapping__c | Text(100) | The care team role that the selected Account record type represents on the care plan. |
Delete Care Team Role on change | mvn__PJN_Delete_Care_Team_Role_on_change__c | Checkbox | When WarningThis field was deprecated in V1.1.0 and added back in V2. This means that this field is available in V1.0.0, V1.0.1, and V2 and above and is not available in V1.1.0, V1.2.0, and V1.3.0. |
Reciprocal Inverse Role | mvn__PJN_Reciprocal_Inverse_Role__c | Text(64) | The care team role that the selected Account record type has a relationship with. WarningThis field has been deprecated as of V1.1.0 and is only available in V1.0.1 and below. |
Reciprocal Inverse Role Case Field | mvn__PJN_Reciprocal_Inverse_Role_Case_Field__c | Text(64) | The API name of the field on the Case object that the reciprocal role maps to. WarningThis field has been deprecated as of V1.1.0 and is only available in V1.0.1 and below. |
Reciprocal Role | mvn__PJN_Reciprocal_Role__c | Text(64) | The care team role that the selected Account record type represents in a reciprocal relationship. |
Reciprocal Role Case Field | mvn__PJN_Reciprocal_Role_Case_Field__c | Text(64) | The API name of the field on the Case object that the selected Account record type maps to. WarningThis field has been deprecated as of V1.1.0 and is only available in V1.0.1 and below. |
The Contact Info Record Types (mvn__PJN_Contact_Info_Record_Types__mdt
) custom metadata type determines which Contact Information (mvn__PJN_Contact_Information__c
) record types are queried in Account Search by grouping the same type of contact information together.
Field label | API name | Data type | Description |
---|---|---|---|
Contact Information Type | mvn__PJN_Contact_Information_Type__c | Picklist | The type of contact information. Picklist values are:
|
Record Types | mvn__PJN_Record_Types__c | Long Text Area(256) | The list of Contact Information ( |
The Data Change Request Criteria (mvn__PJN_Data_Change_Request_Criteria__mdt
) custom metadata type defines the criteria that determine what records should be monitored to trigger the data change request (DCR) functionality on a given object.
Field label | API name | Data type | Description |
---|---|---|---|
Criteria JSON | mvn__PJN_Criteria_JSON__c | Long Text Area(131072) | The JSON string representing the rule that determines whether or not an object matches the specified criteria. WarningReferences to fields in the criteria cannot traverse relationships. Values must be set on the record in question. For guidelines on how to write the JSON criteria, reference Criteria definition. |
DCR Lookup Field | mvn__PJN_DCR_Lookup_Field__c | Text(100) | The API name of the lookup field on the Data Change Request ( |
DCR Record Type Developer Name | mvn__PJN_DCR_Record_Type_Developer_Name__c | Text(100) | The API name of the Data Change Request ( |
SObject | mvn__PJN_SObject__c | Text(100) | The API name of the SObject that the criteria are defined for. |
The Data Change Request Field (mvn__PJN_Data_Change_Request_Field__mdt
) custom metadata type defines the field that should be monitored when the record of a given object meets the criteria for the data change request (DCR) functionality.
Field label | API name | Data type | Description |
---|---|---|---|
Data Change Request Criteria | mvn__PJN_Data_Change_Request_Criteria__c | Metadata Relationship(Data Change Request Criteria) | The related Data Change Request Criteria ( |
Field API Name | mvn__PJN_Field_API_Name__c | Text(100) | The API name of the field that should be monitored for changes. |
The DocuSign One Click Recipient (mvn__DocuSign_One_Click_Recipient__mdt
) custom metadata type defines the type of recipient for a given DocuSign One Click Setting (mvn__DocuSign_One_Click_Setting__mdt
) metadata record.
Field label | API name | Data type | Description |
---|---|---|---|
DocuSign One Click Setting | mvn__DocuSign_One_Click_Setting__c | Metadata Relationship(DocuSign One Click Setting) | The related DocuSign One Click Setting ( |
DocuSign Role | mvn__DocuSign_Role__c | Text(255) | The role that the recipient should have on the DocuSign envelope. WarningThis must match one of the roles configured in the DocuSign template. |
Path to Recipient Email | mvn__Path_to_Recipient_Email__c | Text(255) | The path to the field that defines the recipient's email address. The path can reference fields on other objects as well as traverse relationships. |
Path to Recipient Name | mvn__Path_to_Recipient_Name__c | Text(255) | The path to the field that defines the recipient's name. The path can reference fields on other objects as well as traverse relationships. |
Path to Recipient Phone | mvn__Path_to_Recipient_Phone__c | Text(255) | The path to the field that defines the recipient's phone number. The path can reference fields on other objects as well as traverse relationships. |
Type | mvn__Type__c | Picklist | The type of recipient. Picklist values are:
|
The DocuSign One Click Setting (mvn__DocuSign_One_Click_Setting__mdt
) custom metadata type customizes the email that is sent to recipients for eSignatures and ensures that the eSignatures apply to the appropriate DocuSign templates.
Field label | API name | Data type | Description |
---|---|---|---|
DocuSign Status Lookup to Object | mvn__DocuSign_Status_Lookup_to_Object__c | Text(255) | The API name of the field on the DocuSign Status ( |
Email Message | mvn__Email_Message__c | Long Text Area(32768) | The body of the email to be sent to recipients. |
Email Subject | mvn__Email_Subject__c | Text(255) | The subject of the email to be sent to recipients. |
Matching Rule | mvn__Matching_Rule__c | Long Text Area(131072) | The JSON string describing the criteria that must be matched in order for the DocuSign envelope to be sent for eSignatures. If there are multiple matching rules set, the first one is used. If no matching rule is set, then an exception error will be thrown. WarningFor guidelines on how to write the JSON criteria, reference Criteria definition. |
Template Name | mvn__Template_Name__c | Text(100) | The name of the DocuSign template to be sent for eSignatures. This is used to find the ID of the DocuSign template. |
The DocuSign OneClick Envelope Update (mvn__DocuSign_OneClick_Envelope_Update__mdt
) custom metadata type defines the DocuSign envelope event that triggers an update to the source object defined in the related DocuSign One Click Setting (mvn__DocuSign_One_Click_Setting__mdt
) metadata record.
Warning
The DocuSign OneClick Envelope Update custom metadata type only supports setting static values on the source object. To set dynamic values, consider creating a custom flow.
Field label | API name | Data type | Description |
---|---|---|---|
DocuSign OneClick Setting | mvn__DocuSign_OneClick_Setting__c | Metadata Relationship(DocuSign One Click Setting) | The related DocuSign One Click ( |
Envelope Event | mvn__Envelope_Event__c | Picklist | The envelope event that should trigger the update on the source object. Picklist values are:
|
Field to Update | mvn__Field_to_Update__c | Text(255) | The API name of the field on the source object to update. |
Value to write | mvn__Value_to_Write__c | Text(255) | The static value to set on the field on the source object. |
The Enrollment Field Set (mvn__PJN_Enrollment_Field_Set__mdt
) custom metadata type defines the attributes for the fields used in an Enrollment Wizard Record Form. It is used for the fifth step in configuring the Enrollment Wizard.
Field label | API name | Data type | Description |
---|---|---|---|
Enrollment Wizard Record Form | mvn__PJN_Enrollment_Wizard_Record_Form__c | Metadata Relationship(Enrollment Wizard Record Form) | The Enrollment Wizard Record Form ( |
Field API Name | mvn__PJN_Field_API_Name__c | Text(255) | The API name of the field on the object. |
Is Required | mvn__PJN_Is_Required__c | Checkbox | When set to |
Order | mvn__PJN_Order__c | Number(18, 0) | The order that the field is displayed in the Enrollment Wizard Record Form. Fields are displayed from left to right in two columns. |
The Enrollment Wizard Component (mvn__PJN_Enrollment_Wizard_Component__mdt
) custom metadata type defines the components that are displayed in an Enrollment Wizard Step. A single Enrollment Wizard Step can have one or more components. Components can be Aura components, record forms for data entry, or record lists for data display. It is used for the third step in configuring the Enrollment Wizard.
Field label | API name | Data type | Description |
---|---|---|---|
Component To Load | mvn__PJN_Component_To_Load__c | Text(255) | The API name of the Lightning Component to display. Possible values are:
|
Enrollment Wizard Step | mvn__PJN_Enrollment_Wizard_Step__c | Metadata Relationship(Enrollment Wizard Step) | The Enrollment Wizard Step ( |
Order | mvn__PJN_Order__c | Number(3, 0) | The order that the component is displayed in the given Enrollment Wizard Step. |
Section Title | mvn__PJN_Section_Title__c | Text(128) | The title of the section that the component creates. |
The Enrollment Wizard Record Form (mvn__PJN_Enrollment_Wizard_Record_Form__mdt
) custom metadata type defines the record form that is displayed in an Enrollment Wizard Component to capture data for a given object. It is used for the fourth step in configuring the Enrollment Wizard.
Field label | API name | Data type | Description |
---|---|---|---|
Care Plan Lookup Field API Name | mvn__PJN_Care_Plan_Lookup_Field_API_Name__c | Text(32) | The API name of the field on the object that relates the record to a parent Care Plan record. If the record is a Care Plan record instead of a child record of a parent Care Plan record, then this should be left blank. |
Edit Care Plan Record Form | mvn__PJN_Edit_Care_Plan_Record_Form__c | Checkbox | When set to |
Enrollment Wizard Component | mvn__PJN_Enrollment_Wizard_Component__c | Metadata Relationship(Enrollment Wizard Component) | The Enrollment Wizard Component ( |
RecordType DeveloperName | mvn__PJN_RecordType_DeveloperName__c | Text(255) | The API name of the record type of the new records being created, if applicable. |
SObject API Name | mvn__PJN_SObject_API_Name__c | Text(255) | The API name of the object that the record form is capturing data for. If the record form is used to create new or edit existing Care Plan records, then this should be set to |
The Enrollment Wizard Record List (mvn__PJN_Enrollment_Wizard_Record_List__mdt
) custom metadata type defines the record list that is displayed in an Enrollment Wizard Component to present data for a given object, including data that is captured through an Enrollment Wizard Record Form. It is used for the sixth step in configuring the Enrollment Wizard.
Field label | API name | Data type | Description |
---|---|---|---|
Care Plan Lookup Field API Name | mvn__PJN_Care_Plan_Lookup_Field_API_Name__c | Text(64) | The API name of the field on the object that relates the record to a parent Care Plan record. If the record is a Care Plan record instead of a child record of a parent Care Plan record, then this should be left blank. |
Deletable | mvn__PJN_Deletable__c | Checkbox | When set to |
Editable | mvn__PJN_Editable__c | Checkbox | When set to NoteAny record list that is editable should have a corresponding Enrollment Wizard Record Form where records can be edited. |
Enrollment Wizard Component | mvn__PJN_Enrollment_Wizard_Component__c | Metadata Relationship(Enrollment Wizard Component) | The Enrollment Wizard Component ( |
Fields | mvn__PJN_Fields__c | Long Text Area(1000) | The list of fields to display in the record list. Separate each field with a comma ( |
Order By | mvn__PJN_Order_By__c | Long Text Area(1000) | The order that the fields will display in the record list, from left to right. |
RecordType DeveloperName | mvn__PJN_RecordType_DeveloperName__c | Text(255) | The API name of the record type of the records being displayed, if applicable. |
SObject API Name | mvn__PJN_SObject_API_Name__c | Text(255) | The API name of the object that the record list is displaying data for. If the record list is used to display Care Plan records, then this should be set to |
Where Clause | mvn__PJN_Where_Clause__c | Long Text Area(1000) | The fields used to filter the records that are displayed in the list. |
The Enrollment Wizard Setting (mvn__PJN_Enrollment_Wizard_Setting__mdt
) custom metadata type defines the specific care program that an Enrollment Wizard belongs to. It is used for the first step in configuring the Enrollment Wizard.
Field label | API name | Data type | Description |
---|---|---|---|
Program DeveloperName | mvn__PJN_Program_DeveloperName__c | Text(255) | The API name of the Program ( |
The Enrollment Wizard Step (mvn__PJN_Enrollment_Wizard_Step__mdt
) custom metadata type defines the screens that are displayed in an Enrollment Wizard. Each screen should represent a unique data element for which information is entered, such as Insurance, Prescription, Medical History, or Consent. It is used for the second step in configuring the Enrollment Wizard.
Field label | API name | Data type | Description |
---|---|---|---|
Enrollment Wizard Setting | mvn__PJN_Enrollment_Wizard_Setting__c | Metadata Relationship(Enrollment Wizard Setting) | The Enrollment Wizard Setting ( |
Order | mvn__PJN_Order__c | Number(3, 0) | The order that the screen is displayed in the Enrollment Wizard. |
The ePA Field Mapping (mvn__PJN_Epa_Field_Mapping__mdt
) custom metadata type defines the field values to be mapped to an electronic prior authorization (ePA) vendor's JSON key.
Field label | API name | Data type | Description |
---|---|---|---|
ePA Field API Path | mvn__PJN_Field_API_Path__c | Text(255) | The path to the source field that contains data to be sent to the ePA vendor. The path can reference fields on other objects as well as traverse relationships. |
ePA Interface Handler | mvn__PJN_ePA_Interface_Handler__c | Metadata Relationship(Interface Handler) | The related Interface Handler ( |
Is Required? | mvn__PJN_Is_Required__c | Checkbox | If |
Vendor JSON Key | mvn__PJN_Vendor_Json_Key__c | Text(100) | The JSON key name that is expected by the ePA vendor. |
The Event Rollup (mvn__PJN_Event_Rollup__mdt
) custom metadata type defines the Event (mvn__PJN_Event__c
) record types whose fields should roll up to their parent Case records.
Field label | API name | Data type | Description |
---|---|---|---|
Event Record Type | mvn__PJN_Event_Record_Type__c | Text(100) | The API name of the Event ( NoteThis should not include any namespace. |
The Event Rollup Mapping (mvn__PJN_Event_Rollup_Mapping__mdt
) custom metadata type defines the mapping between Event (mvn__PJN_Event__c
) fields and the parent Case fields.
Field label | API name | Data type | Description |
---|---|---|---|
Event Rollup | mvn__PJN_Event_Rollup__c | Metadata Relationship(Event Rollup) | The related Event Rollup ( |
Source Event Field | mvn__PJN_Source_Event_Field__c | Text(100) | The API name of the Event ( NoteThis should include any namespace as appropriate. |
Target Case Field | mvn__PJN_Target_Case_Field__c | Text(100) | The API name of the Case field whose value is mapped by the Source Event Field. NoteThis should include any namespace as appropriate. |
The Feature Activation (mvn__Feature_Activation__mdt
) custom metadata type controls which features are turned on and off. Each Feature Activation metadata record represents a separate feature that can be activated.
Field label | API name | Data type | Description |
---|---|---|---|
Active | mvn__Active__c | Checkbox | When set to NoteFor all Feature Activation metadata records that are provided out of the box, the Active field equals |
The Field Setting (mvn__PJN_Field_Setting__mdt
) custom metadata type defines the fields displayed in Account Search that users can use as search parameters and that users see in the search results.
Field label | API name | Data type | Description |
---|---|---|---|
Account Record Type | mvn__PJN_Account_Record_Type__c | Text(57) | The API name of the associated Account record type. When set to |
Contact Info Record Type | mvn__PJN_Contact_Info_Record_Type__c | Text(57) | The API name of the associated Contact Information record type if the selected Object is Contact Information ( |
Field | mvn__PJN_Field__c | Text(60) | The API name of the field. |
Is Person Record Type? | mvn__PJN_Is_Person_Record_Type__c | Checkbox | When set to |
Object | mvn__PJN_Object__c | Picklist | The API name of the object that the field is on. Possible values are:
|
Search Field Order | mvn__PJN_Search_Field_Order__c | Number(2, 0) | The order that the field appears in the search parameters. Numbers run from left to right across three columns. If blank, the field is hidden from the search parameters. |
Search Results Order | mvn__PJN_Search_Results_Order__c | Number(3, 0) | The order that the field appears in the search results. Numbers run from left to right. If blank, the field is hidden from the search results. |
Show in Primary Results | mvn__PJN_Show_in_Primary_Results__c | Checkbox | When set to WarningThis field has been deprecated as of Komodo Care Connect V2.1.0. |
The File Rollup Setting (mvn__PJN_File_Rollup_Setting__mdt
) custom metadata type identifies objects whose files will roll up to a parent care plan. Files uploaded to records of such objects are automatically related to the parent Care Plan (Case
) record and appear in both the original record and the Care Plan (Case
) record.
Field label | API name | Data type | Description |
---|---|---|---|
Parent Lookup Field API Name | mvn__PJN_Parent_Lookup_Field_API_Name__c | Text(100) | The API name of the lookup field on the sObject that relates to the parent Care Plan ( |
sObject API Name | mvn__PJN_sObject_API_Name__c | Text(100) (Unique Case Insensitive) | The API name of the sObject that is related to a Care Plan ( |
The Fulfillment Request Creation (mvn__PJN_Fulfillment_Request_Creation__mdt
) custom metadata type defines the records and fields from which data for a fulfillment request are pulled.
Field label | API name | Data type | Description |
---|---|---|---|
Care Plan Source Field API Name | mvn__PJN_Care_Plan_Source_Field_API_Name__c | Text(255) | The API name of the lookup field on a Care Plan ( |
Mapping Object Type Name | mvn__PJN_Mapping_Object_Type_Name__c | Text(255) | The value of the Source Object Type Name field on the corresponding Mapping ( |
Program | mvn__PJN_Program__c | Metadata Relationship(Program) | The related Program ( |
Record Type Developer Name | mvn__PJN_Record_Type_Developer_Name__c | Text(255) | The API name of the Fulfillment Request ( |
Request Target Field API Name | mvn__PJN_Request_Target_Field_API_Name__c | Text(255) | The API name of the lookup field on a Fulfillment Request ( |
The Global Setting (mvn__PJN_Global_Setting__mdt
) custom metadata type defines the Account and Contact Information (mvn__PJN_Contact_Information__c
) records available to be searched in Account Search.
Warning
This custom metadata type and all of its fields have been deprecated as of V1.3.0 and are only available in V1.2.0 and below. This custom metadata type is superseded by the Contact Info Record Types (mvn__PJN_Contact_Info_Record_Types__mdt
) custom metadata type.
Note
The Global Setting custom metadata type is used for all Programs.
Field label | API name | Data type | Description |
---|---|---|---|
Account Search Account Status | mvn__PJN_Account_Search_Account_Status__c | Text(255) | The list of statuses in Account Search that are allowed to search Account records. Separate each status with a comma ( |
Account Search Contact Info Status | mvn__PJN_Account_Search_Contact_Info_Status__c | Text(255) | The list of statuses in Account Search that are allowed to search Contact Information ( |
Account Search Handler Classes | mvn__PJN_Account_Search_Handler_Classes__c | Text(255) | 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 WarningThis field has been deprecated as of V1.1.0 and is only available in V1.0.1 and below. |
Account Search Max Results | mvn__PJN_Account_Search_Max_Results__c | Number(3, 0) | The maximum number of search results returned by Account Search. This cannot exceed the SOSL limit of 200. WarningThis field has been deprecated as of V1.1.0 and is only available in V1.0.1 and below. |
Contact Info Address Record Types | mvn__PJN_Contact_Info_Address_Record_Types__c | Text(255) | The list of all Contact Information ( |
Contact Info Email Record Types | mvn__PJN_Contact_Info_Email_Record_Types__c | Text(255) | The list of all Contact Information ( |
Contact Info Fax Record Types | mvn__PJN_Contact_Info_Fax_Record_Types__c | Text(255) | The list of all Contact Information ( |
Contact Info Phone Record Types | mvn__PJN_Contact_Info_Phone_Record_Types__c | Text(255) | The list of all Contact Information records ( |
Create DCR | mvn__PJN_Create_DCR__c | Checkbox | When set to |
Include Open Data Network? | mvn__PJN_Include_Open_Data_Network__c | Checkbox | When set to |
Transaction Log Level | mvn__PJN_Transaction_Log_Level__c | Text(50) | The transaction log level. Possible values are:
|
The Interface Handler (mvn__Interface_Handler__mdt
) custom metadata type defines the custom implementation of a given interface.
Field label | API name | Data type | Description |
---|---|---|---|
Active | mvn__Active__c | Checkbox | When |
Class | mvn__Class__c | Text(40) | The name of the class that implements the interface. WarningClass names are case sensitive. |
Class Namespace | mvn__Class_Namespace__c | Text(15) | The namespace of the class that implements the interface. WarningNamespaces are case sensitive. |
Context | mvn__Context__c | Text(40) | The context within Komodo Care Connect that the interface will be used. This is one way to determine where the handler will be used, especially if multiple interfaces are called. WarningContext names are case sensitive. |
Criteria | mvn__Criteria__c | Long Text Area(32768) | The JSON criteria that determines when the implementation should be used. |
Interface | mvn__Interface__c | Text(40) | The API name of the interface that is being implemented. This is one way to determine where the handler will be used and the primary way to query interface handlers. WarningInterface names are case sensitive. |
Sequence | mvn__Sequence__c | Number(6, 0) | The sequence that the classes will be called in if there are multiple classes configured. |
The Lead Mapping Field (mvn__PJN_Lead_Mapping_Field__mdt
) custom metadata type defines the fields on the Lead standard object that should be searchable by the PJN_LeadSearchHdlr handler as well as the objects and fields that Account Search should map results to.
Note
The name of the Lead Mapping Field metadata record must match an existing field on the Lead standard object.
Field label | API name | Data type | Description |
---|---|---|---|
Contact Info Record Type | mvn__PJN_Contact_Info_Record_Type__c | Text(100) | The API name of the Contact Information ( |
Contact Info Type | mvn__PJN_Contact_Info_Type__c | Text(100) | The Type ( |
Map to Field | mvn__PJN_Map_to_Field__c | Text(100) | The target field on which the Lead field should map values to. |
Map to Object | mvn__PJN_Map_to_Object__c | Picklist | The target object on which the Lead object should map values to. Picklist values are:
|
The Mapping (mvn__PJN_Mapping__mdt
) custom metadata type defines the type of mapping that is to be executed. This is used for the second step in setting up the Mapping Engine.
Field label | API name | Data type | Description |
---|---|---|---|
Always Runs | mvn__PJN_Always_Runs__c | Checkbox | When set to |
Mapping Job | mvn__PJN_Mapping_Job__c | Metadata Relationship(Mapping Job) | The related Mapping Job ( |
Mapping Type | mvn__PJN_Mapping_Type__c | Picklist | The type of value to be mapped. For Fulfillment Request ( |
Source Object API Name | mvn__PJN_Source_Object_API_Name__c | Text(255) | The API name of the object from which the value to be mapped is derived. |
Source Object Type Name | mvn__PJN_Source_Object_Type_Name__c | Text(255) | The link between the source record and the possible mapping types. The predefined values to use are listed below in Table 166, “Source Object Type Name values”. They allow labels, dates, and field values to be sourced from different objects. |
Value | Description |
---|---|
| Used for Label, Date, or Record Type mappings that don't have a source object to map from. |
| Used when a Field, Label, or Date value is sourced from the parent Patient. |
| Used when a Field, Label, or Date value is sourced from the parent Care Plan. |
| Used when a Field, Label, or Date value is sourced from the parent Program. |
| Used when a Field, Label, or Date value is sourced from the parent Program Problem. |
| Used when a Field, Label, or Date value is sourced from the parent Program Case. |
| Used when a Field, Label, or Date value is sourced from the parent Zip-to-Team record. |
The Mapping Date Formula (mvn__PJN_Mapping_Date_Formula__mdt
) custom metadata type defines the source date value and the target field for a mapping of the Date Formula
mapping type. The source date value to be mapped is either derived from a formula or a date field and can be adjusted with the Days To Add (mvn__PJN_Days_To_Add__c
) field and the Default Business Hours record. The Mapping Date Formula custom metadata type is used for the fifth step in setting up the Mapping Engine.
Out of the box, the Mapping Engine only uses the Days to Add field when calculating and stamping the final date value onto the target field. However, you can configure the Mapping Engine so that it also uses the Default Business Hours record to determine which days of the week are used to calculate the final date and ensure that the final date falls on a working day. For example, if the Default Business Hours record is modified to exclude Saturday and Sunday, the current day is a Tuesday, and an activity is created to be due five days from today, then the Mapping Engine will calculate the activity to be due on the following Tuesday. This is because the Mapping Engine will not include Saturday and Sunday in its calculation. The same concept applies even if the value on the Days to Add field is a negative number. For example, if the Default Business Hours record only excludes Saturday, the current day is a Wednesday, and the number of days to add is -5, such as five days before another fixed date on a care plan, then the Mapping Engine will calculate the final day to fall on a Thursday.
To configure the Mapping Engine to use the Default Business Hours record, turn on the Mapping Engine Business Hours feature.
In Setup, navigate to the Feature Activation (
mvn__Feature_Activation__mdt
) custom metadata type.Click Manage Feature Settings.
Click the Mapping Engine Business Hours (
Mapping_Engine_Business_Hours
) metadata record.Edit the metadata record and check the Active checkbox.
Click Save.
Field label | API name | Data type | Description |
---|---|---|---|
Days To Add | mvn__PJN_Days_To_Add__c | Number(5, 0) | The number to be added to the date provided in either the Formula field or the Source Field API Name field. Negative numbers are permitted. |
Formula | mvn__PJN_Formula__c | Picklist | The formula from which the date value to be mapped is derived. Possible values are:
|
Mapping | mvn__PJN_Mapping__c | Metadata Relationship(Mapping) | The related Mapping ( |
Source Field API Name | mvn__PJN_Source_Field_API_Name__c | Text(255) | The API name of the field from which the date value to be mapped is derived. This field is required if the selected value in the Formula field is |
Target Field API Name | mvn__PJN_Target_Field_API_Name__c | Text(255) | The API name of the field to which the date value is mapped. |
The Mapping Field (mvn__PJN_Mapping_Field__mdt
) custom metadata type defines the source field and target field for a mapping of the Field
Mapping Type. This is used for the third step in setting up the Mapping Engine.
Field label | API name | Data type | Description |
---|---|---|---|
Mapping | mvn__PJN_Mapping__c | Metadata Relationship(Mapping) | The related Mapping ( |
Source Field API Name | mvn__PJN_Source_Field_API_Name__c | Text(255) | The API name of the field from which the value to be mapped is derived. |
Target Field API Name | mvn__PJN_Target_Field_API_Name__c | Text(255) | The API name of the field to which the mapped value is written. |
The Mapping Job (mvn__PJN_Mapping_Job__mdt
) custom metadata type defines the object that a mapping will be executed against. This is used for the first step in setting up the Mapping Engine.
Field label | API name | Data type | Description |
---|---|---|---|
Is Active | mvn__PJN_Is_Active__c | Checkbox | When set to |
Target Object API Name | mvn__PJN_Target_Object_API_Name__c | Text(255) | The API name of the object onto which the values will be mapped. |
The Mapping Label (mvn__PJN_Mapping_Label__mdt
) custom metadata type defines the source label value and the target field for a mapping of the Label
Mapping Type. The value to be mapped is either derived from a label text or a source field. This is used for the fourth step in setting up the Mapping Engine.
Field label | API name | Data type | Description |
---|---|---|---|
Label Text | mvn__PJN_Label_Text_Area__c | Long Text Area(32768) | The text to be written into the target field if the value to be mapped is not derived from a source field. |
Mapping | mvn__PJN_Mapping__c | Metadata Relationship(Mapping) | The related Mapping ( |
Source Field API Name | mvn__PJN_Source_Field_API_Name__c | Text(255) | The API name of the field from which the label value to be mapped is derived. |
Target Field API Name | mvn__PJN_Target_Field_API_Name__c | Text(255) | The API name of the field to which the mapped value is written. |
Target Field Type | mvn__PJN_Target_Field_Type__c | Picklist | The data type that source string values will be parsed into to be mapped into non-string target fields. For the boolean data type, use either |
The Mapping Queue (mvn__PJN_Mapping_Queue__mdt
) custom metadata type sets the queue on the target record for a mapping of the Queue
Mapping Type. The queue is set to the owner of the record being created. This is used for the sixth step in setting up the Mapping Engine.
Field label | API name | Data type | Description |
---|---|---|---|
Mapping | mvn__PJN_Mapping__c | Metadata Relationship(Mapping) | The related Mapping ( |
Queue API Name | mvn__PJN_Queue_API_Name__c | Text(255) | The API name of the queue to be applied to the target record. |
Target Field API Name | mvn__PJN_Target_Field_API_Name__c | Text(255) | The API name of the object’s record type field: |
The Mapping Record Type (mvn__PJN_Mapping_Record_Type__mdt
) custom metadata type defines the record type for the target field in a mapping of the Record Type
Mapping Type. This is used for the seventh step in setting up the Mapping Engine.
Field label | API name | Data type | Description |
---|---|---|---|
Mapping | mvn__PJN_Mapping__c | Metadata Relationship(Mapping) | The related Mapping ( |
Record Type API Name | mvn__PJN_Record_Type_API_Name__c | Text(255) | The API name of the record type to apply to the mapped record. |
Target Field API Name | mvn__PJN_Target_Field_API_Name__c | Text(255) | The API name of the object’s record type field: |
The Medical History Component Field Set (mvn__PJN_Medical_History_Component_Field_Set__mdt
) custom metadata type determines which fields on the Medical History (mvn__PJN_Medical_History__c
) object should appear as columns for a specific tab in the Medical History (pjnMedicalHistory
) component. Each Medical History record type represents a tab, and each Medical History field set contains the fields to appear as columns in the tab.
Field label | API name | Data type | Description |
---|---|---|---|
Field Set Name | mvn__PJN_Field_Set_Name__c | Text(50) | The API name of a Medical History ( |
Record Type | mvn__PJN_Record_Type__c | Text(50) (Unique Case Insensitive) | The API name of a Medical History ( |
The Merge Tool Setting (mvn__PJN_Merge_Tool_Setting__mdt
) custom metadata type controls the objects that appear in the Care Plan Child Record screen of the Patient Merge Tool, including custom objects. Each object is a child object of a care plan to be merged and has its own table listing records related to the care plan.
Field label | API name | Data type | Description |
---|---|---|---|
Child SObject API Name | mvn__PJN_Child_SObject_API_Name__c | Text(64) | The API name of the child object of the care plan. |
Field API Name to Account | mvn__PJN_Field_API_Name_to_Account__c | Text(255) | The API name of the field on the child object that relates to the associated Account record. |
Field API Name To Care Plan | mvn__PJN_Field_API_Name_To_Care_Plan__c | Text(64) | The API name of the field on the child object that relates to the associated Case record. This cannot be blank as all care plan child records must be related to a care plan. |
Field List | mvn__PJN_Field_List__c | Text(255) | The list of fields that appear as columns in the child object's table of records. |
Order | mvn__PJN_Order__c | Number(3, 0) | The order that the child object's table of records appears in the Care Plan Child Record screen. |
The Missing Information Config (mvn__PJN_Missing_Information_Config__mdt
) custom metadata type checks the fields in a given care plan to determine if the care plan is missing information.
Warning
This custom metadata type and all of its fields have been deprecated as of Komodo Care Connect V2.1.0. This custom metadata type is superseded by the Missing Information Configuration (mvn__PJN_Missing_Information_Config__mdt
) custom metadata type.
Field label | API name | Data type | Description |
---|---|---|---|
Display Text | mvn__PJN_Field_Label__c | Text(255) | The field that is missing information. This appears in the Missing Information ( |
Field Path | mvn__PJN_Field_Path__c | Text(255) | The API name of the field that is to be checked for missing information. It can traverse lookups to reference fields outside of the Care Plan ( |
Program | mvn__PJN_Program__c | Metadata Relationship(Program) | The related Program ( |
The Missing Information Configuration (mvn__PJN_Missing_Information_Configuration__mdt
) custom metadata type specifies the fields that should be checked for missing information. Missing Information Configuration metadata records that are created for the same object, record type, and program are related to the same Missing Information Group (mvn__PJN_Missing_Information_Group__mdt
) metadata record. This custom metadata type is used to configure the functionality to check for missing information.
Field label | API name | Data type | Description |
---|---|---|---|
Display Text | mvn__PJN_Field_Label__c | Text(255) | The label of the field that is missing information. This appears in the Missing Information ( |
Field Path | mvn__PJN_Field_Path__c | Text(255) | The API name of the field or field path that is to be checked for missing information. The field can be on any object; this can traverse object relationships such that the field being referenced does not have to be present on the starting object. |
Missing Information Group | mvn__PJN_Missing_Information_Group__c | Metadata Relationship(Missing Information Group) | The related Missing Information Group ( |
The Missing Information Group (mvn__PJN_Missing_Information_Group__mdt
) custom metadata type groups Missing Information Configuration (mvn__PJN_Missing_Information_Configuration__mdt
) metadata records together based on which object, record type, and program is to be checked for missing information. This custom metadata type is used to configure the functionality to check for missing information.
Field label | API name | Data type | Description |
---|---|---|---|
Object | mvn__PJN_Object__c | Text(255) | The API name of the object that the group of missing information configuration(s) belongs to. |
Program | mvn__PJN_Program__c | Metadata Relationship(Program) | The related Program ( |
Record Type | mvn__PJN_Record_Type__c | Text(255) | The API name of the object record type that the group of missing information configuration(s) belongs to. If there are no record types on the object, this can be left blank. |
The New Account Fields Setting (mvn__PJN_New_Account_Fields_Setting__mdt
) custom metadata type defines the fields that are displayed in the New Account modal for a given account type.
Field label | API name | Data type | Description |
---|---|---|---|
Field API Name | mvn__PJN_Field_API_Name__c | Text(255) | The API name of the field. |
Order | mvn__PJN_Order__c | Number(3, 0) | The order that the field appears in the New Account modal. Numbers run from left to right across two columns. |
Record Type | mvn__PJN_Record_Type__c | Picklist | The associated Account record type. Possible values are:
|
Required | mvn__PJN_Required__c | Checkbox | When set to |
The New Contact Info Fields Settings (mvn__PJN_New_Contact_Info_Fields_Setting__mdt
) custom metadata type defines the fields that appear in the New Contact Information modal in Account Search for a given contact information type.
Field label | API name | Data type | Description |
---|---|---|---|
Field API Name | mvn__PJN_Field_API_Name__c | Text(32) | The API name of the field. |
Order | mvn__PJN_Order__c | Number(3, 0) | The order that the field is displayed in the New Contact Information modal. Numbers run from left to right across two columns. |
Record Type | mvn__PJN_Record_Type__c | Picklist | The API name of the Contact Information (
|
Required | mvn__PJN_Required__c | Checkbox | When set to |
Type | mvn__PJN_Type__c | Picklist | The type of the field. Possible values are:
|
The Program (mvn__PJN_Program__mdt
) custom metadata type defines the program journey that patients can enroll in.
Field label | API name | Data type | Description |
---|---|---|---|
Missing Enrollment Info Problem | mvn__PJN_Missing_Enrollment_Info_Problem__c | Text(40) | The API name of the Program Problem ( |
Zip to Team Address Field Paths | mvn__PJN_Zip_to_Team_Address_Field_Paths__c | Long Text Area(32768) | A comma-separated list of Case fields that look up to Contact Information ( |
The Program Case (mvn__PJN_Program_Case__mdt
) custom metadata type defines the activities within each program problem, or stage, of a patient's journey. Program cases represent standard Salesforce Cases and are created when a new stage begins or a previous activity in the current stage is completed.
Note
"Program case" and "activity" may be used interchangeably.
Field label | API name | Data type | Description |
---|---|---|---|
Order | mvn__PJN_Order__c | Number(2, 0) | The order in which the program case appears in the care plan path for an enrolled patient. |
Program Problem | mvn__PJN_Program_Problem__c | Metadata Relationship(Program Problem) | The related Program Problem ( |
The Program Case Dependency (mvn__PJN_Program_Case_Dependency__mdt
) custom metadata type defines the dependency between different program cases within a single program problem, or stage, where a case that is dependent on another case is only created when the controlling case is canceled or completed (Closed
).
Field label | API name | Data type | Description |
---|---|---|---|
Dependent | mvn__PJN_Dependent__c | Metadata Relationship(Program Case) | The dependent program case. |
Dependent On | mvn__PJN_Dependent_On__c | Metadata Relationship(Program Case) | The controlling program case. |
The Program Problem (mvn__PJN_Program_Problem__mdt
) custom metadata type defines the attributes of the problems, or stages, that comprise a program.
Note
"Problem" and "stage" may be used interchangeably.
Field label | API name | Data type | Description |
---|---|---|---|
Hide New Activity Button | mvn__PJN_Hide_New_Activity_Button__c | Checkbox | When set to |
Is Library | mvn__PJN_Is_Library__c | Checkbox | When set to WarningThis field has been deprecated as of V2.1.0 and is only available in V2.0.0 and below. |
Is Removable | mvn__PJN_Is_Removable__c | Checkbox | When set to NoteA stage can only be removed if it has not yet been initiated. When a stage is removed, the stage and its activities are deleted. |
Is Skippable | mvn__PJN_Is_Skippable__c | Checkbox | When set to NoteWhen a stage is skipped, the stage and its related activities are closed as |
Is Standard | mvn__PJN_Is_Standard__c | Checkbox | When set to WarningThis field has been deprecated as of V2.1.0 and is only available in V2.0.0 and below. |
Is Startable | mvn__PJN_Is_Startable__c | Checkbox | When set to |
Library Order | mvn__PJN_Library_Order__c | Number(3, 0) | The order in which the program problem appears in the care plan stage library for an enrolled patient. If blank, the problem will not appear in the library as an optional stage for the care plan. |
New Activity Button Override | mvn__PJN_New_Activity_Button_Override__c | Long Text Area(32768) | A list of comma-separated key-value pairs to configure the New Activity button. The format is The first key-value pair will be the main button. All other key-value pairs will appear in a dropdown menu. If this field is left blank, Case records of the |
Order | mvn__PJN_Order__c | Number(3, 0) | The order in which the program problem appears in the care plan progress bar for an enrolled patient. If blank, the problem will not appear in the care plan path as a default stage for the care plan. |
Program | mvn__PJN_Program__c | Metadata Relationship(Program) | The related Program ( |
The Relationship Role Configuration (mvn__PJN_Relationship_Role_Configuration__mdt
) custom metadata type establishes contact-contact relationships and account-contact relationships by relating two Case Field Configuration (mvn__PJN_Case_Field_Configuration__mdt
) custom metadata records.
Note
The order in which the two Case Field Configuration records identified in the mvn__PJN_Start_From_Account__c
and mvn__PJN_Connect_To_Account__c
fields does not matter. Depending on whether a Case Field Configuration record represents a Business Account or a Person Account, the Relationship Role Configuration custom metadata type will create a Contact-Contact Relationship (HealthCloudGA__ContactContactRelation__c
) record or a Account Contact Relationship (AccountContactRelation
) record and Salesforce will create a reciprocal relationship as appropriate.
Field label | API name | Data type | Description |
---|---|---|---|
Connect To Account | mvn__PJN_Connect_To_Account__c | Metadata Relationship(Case Field Configuration) | The Case Field Configuration ( |
Role | mvn__PJN_Role__c | Text(255) | The role of the contact in a relationship with an account (i.e., Business Account), such as a general practitioner to a hospital. |
Start From Account | mvn__PJN_Start_From_Account__c | Metadata Relationship(Case Field Configuration) | The Case Field Configuration ( |
The Trigger Handler Setting (mvn__PJN_Trigger_Handler_Setting__mdt
) custom metadata type defines the execution of triggers. For the list of available trigger handler classes, reference Trigger handler exceptions.
Field label | API name | Data type | Description |
---|---|---|---|
Active | mvn__PJN_Active__c | Checkbox | When |
Class | mvn__PJN_Class__c | Text(255) | The Apex class that the trigger is related to. |
Event | mvn__PJN_Event__c | Picklist | The Apex trigger event. |
Order | mvn__PJN_Order__c | Number(3, 0) | The order that the trigger should execute in. |
SObject API Name | mvn__PJN_SObject_API_Name__c | Text(255) | The object that the trigger is related to. |