Table 186, “Record-triggered flows” below shows all of the active record-triggered flows that Komodo Care Connect provides out of the box. The Overridable attribute for every flow is set to true such that they can be overridden with custom modifications. For more information, reference Salesforce's documentation on Create a Managed-Installed Flow That Admins Can Override and Customize.
To override a flow that Komodo Care Connect provides out of the box:
In Setup, search for and select Flows.
Click the Flow label of the Komodo Care Connect flow to override. The flow will open in the Flow Builder.
Modify the flow as desired.
Click Save As. The "Save as flow override" modal will open.
Enter the Flow Label and the Flow API Name of the flow override.
Click Save.
Click Activate to activate the flow override. The custom flow will be linked to and run in place of the out-of-the-box flow.
Table 186. Record-triggered flows
Flow name | Triggering object | Trigger | Description |
|---|
Assistance Program - KCC Before Create Update (mvn__PJN_Assistance_Program_PJN_Before_Create_Update) | Assistance Program (mvn__PJN_Assistance_Program__c) | Record—Run Before Save | This flow runs before a new or modified Assistance Program record is saved. It sets the Account (mvn__PJN_Account__c) field on the Assistance Program record to equal the Account (AccountId) field of the parent Care Plan (Case) record. This means that both the Assistance Program record and the Care Plan record relate to the same Account record. |
Consent - KCC After Create Update (mvn__PJN_Consent_After_Create_Update) | Consent (mvn__PJN_Contact_Point_Type_Consent__c) | Record—Run After Save | This flow runs after a new or modified Consent record is saved. It helps calculate the date on which an individual's written or verbal consent expires based on certain criteria. The flow first checks if the Privacy Consent Status (mvn__PJN_Privacy_Consent_Status__c) field equals Opt In, the Effective From (mvn__PJN_Effective_From__c) field is not null, and the Effective To (mvn__PJN_Effective_To__c) field is null. If these criteria are met, the flow then checks whether the Capture Source Type (mvn__PJN_Capture_Source_Type__c) field equals Written or Verbal. The flow subsequently uses either the Effective Months (Written) (mvn__PJN_Effective_Months__c) field or the Effective Days (Verbal) (mvn__PJN_Effective_Days_Verbal__c) field on the related Data Use Purpose (DataUsePurpose) record, respectively, to add to the Effective From field on the Consent record and update the Effective To field. |
Contact Information - KCC Before Create Update (mvn__PJN_Contact_Information_Before_Create_Update) | Contact Information (mvn__PJN_Contact_Information__c) | Record—Run Before Save | This flow runs before a new or modified Contact Information record is saved. It sets and formats the Value (mvn__PJN_Value__c) field based on the Contact Information record type, and the result is surfaced in the Value column in the Contact Information component. For the Address (PJN_Address) record type, the flow concatenates the Address Line 1 (mvn__PJN_Address_Line_1__c), Address Line 2 (mvn__PJN_Address_Line_2__c), City (mvn__PJN_City__c), State (mvn__PJN_State__c), and Postal Code (mvn__PJN_Postal_Code__c) fields and sets the Value field to equal the result. For the Email (PJN_Email) record type, the flow simply sets the Value field to equal the Email (mvn__PJN_Email__c) field. For the Fax (PJN_Fax) and Phone (PJN_Phone) record types, the flow formats the Phone (mvn__PJN_Phone__c) or Fax (mvn__PJN_Fax__c) field, respectively, to (xxx) xxx-xxxx and sets the Value field to equal the result. |
Event - KCC Before Create Update (mvn__PJN_Event_Before_Create_Update) | Event (mvn__PJN_Event__c) | Record—Run Before Save | This flow runs before a new or modified Event record is saved. If the Event record has a related Case record on the Case (mvn__PJN_Case__c) field, then the flow sets the Program DeveloperName (mvn__PJN_Program_DeveloperName__c) field to equal the Program DeveloperName (mvn__PJN_Program_DeveloperName__c) field on the related Case record. This means that both the Event record and the Case record depend on the same Program (mvn__PJN_Program__mdt) metadata record. |
Prior Authorization: KCC Before Insert (mvn__PJN_Prior_Authorization_Before_Insert) | Prior Authorization (mvn__PJN_Prior_Authorization__c) | Record—Run Before Save | This flow runs before a new Prior Authorization record is saved. It relates the prior authorization to the coverage investigation of the parent member plan based on certain criteria. The flow first checks if there are Coverage Investigation Item (mvn__PJN_Coverage_Investigation_Item__c) records that relate to the parent Member Plan (mvn__PJN_Member_Plan__c) record of the Prior Authorization record and whose Status (mvn__PJN_Status__c) field equals Pending or In Progress. If these criteria are met, the flow then sets the Coverage Investigation (mvn__PJN_Coverage_Investigation__c) field on the Prior Authorization record to relate to the parent Coverage Investigation (mvn__PJN_Coverage_Investigation__c) record of the Coverage Investigation Item records. |
Prior Authorization: KCC Before Insert Update (mvn__PJN_Prior_Authorization_Before_Insert_Update) | Prior Authorization (mvn__PJN_Prior_Authorization__c) | Record—Run Before Save | This flow runs before a new or modified Prior Authorization record is saved. It sets the Care Plan (mvn__PJN_Care_Plan__c) field on the Prior Authorization record to relate to the same Case record as the Care Plan (mvn__PJN_Care_Plan__c) field on the parent Member Plan (mvn__PJN_Member_Plan__c) record. This means that both the Prior Authorization record and the Member Plan record relate to the same Case record. |
Shipment - KCC Before Create Update (mvn__PJN_Shipment_Before_Create_Update) | Shipment (mvn__PJN_Shipment__c) | Record—Run Before Save | This flow runs before a new or modified Shipment record is saved. If the Shipment record has a related Case record on the Care Plan (mvn__PJN_Care_Plan__c) field, then the flow sets the Program DeveloperName (mvn__PJN_Program_DeveloperName__c) field to equal the Program DeveloperName (mvn__PJN_Program_DeveloperName__c) field on the related Case record. This means that both the Shipment record and the Case record depend on the same Program (mvn__PJN_Program__mdt) metadata record. |
Task - KCC Before Create Update (mvn__Task_PJN_Before_Create_Update) | Task (Task) | Record—Run Before Save | This flow runs before a new or modified Task record is saved. Based on the Task record type, it sets and formats fields on the Task record with values from the corresponding Activity record. If the Task record type equals Contact Attempt (PJN_Contact_Attempt), then the flow formats the Subject (Subject) field using the Outcome (mvn__PJN_Outcome__c) field on the corresponding Activity (Activity) record and sets the Due Date (ActivityDate) field to equal the Attempt Date/Time (mvn__PJN_Attempt_Date_Time__c) field on the Activity record. |
Zip To Team - KCC After Create Update (mvn__PJN_Zip_To_Team_After_Create_Update) | Zip To Team (mvn__PJN_Zip_To_Team__c) | Record—Run After Save | This flow runs after a new or modified Zip To Team record is saved. It sets the External ID (mvn__PJN_External_ID__c) field to equal the Key (mvn__PJN_Key__c) field so that both fields on a single Zip To Team record have the same value. |