Activities

Out of the box, there are three Case record types that capture different types of activities:

Each of these record types can be configured so that DocuSign consent can be generated directly from the Case record.

Users can set activities in care plans to repeat so that when the current Activity (PJN_Activity) record is Closed or Cancelled, a new duplicate activity is created in the same stage. The fields that are copied into the new activity are controlled by the Recurring Case Clone Fields (mvn__PJN_Recurring_Case_Clone_Fields) field set. Meanwhile, the due date of the new activity is determined by the mvn__PJN_Next_Activity__c field in the original Case record, which is calculated based on the mvn__PJN_Repeat_Every__c and mvn__PJN_Cadence__c fields and can be overridden by the mvn__PJN_Override_Next_Activity__c field.

To repeat an activity:

To stop an activity from repeating:

In addition to setting recurring activities, users can also trigger Activity (PJN_Activity) records to be automatically created upon a given event. This may be helpful in situations where users need activities to be created based on a date on a record on a parent care plan, such as when a patient's HIPAA consent is expiring in 30 days and the user must begin the renewal process with the patient.

You can configure the automation of activity creation either by adding the mvn__PJN_CarePlanActivityService action in a flow or by calling the createActivities invocable method in the Care Plan Activity Service (PJN_CarePlanActivityService) global Apex class. During the configuration process, you must set the care plan ID and the subject of the new activity in order for the activity to be successfully created. You may choose to also set the values of other fields on the new activity, including, but not limited to, the due date, the owner, and the status.

For each Activity (PJN_Activity) record, specific action items can be further added for users to track and check off. This may be helpful for users who are assigned activities in care plan stages that encompass multiple sub-tasks, such as case managers who have to cover a number of topics in their welcome calls to patients, like checking insurance coverage, gathering communication preferences, and more. All action items are stored in the Action Item (mvn__PJN_Action_Item__c) custom object and appear in the Action Items (pjnActionItems) Lightning Web Component (LWC) on a given Case record page. However, out of the box, the Action Items LWC is only visible on Case records of the Activity (PJN_Activity) record type where there is at least one action item. Users can use the Action Items LWC as long as they have access to the activity and do not have to be the owner or assignee on the activity. The number of child action items for each Case record is tracked on the Action Items Count (mvn__PJN_Action_Items_Count__c) field on the Case object.

Action items can either be standard or custom. Standard action items can only be created, modified, and deleted by admin users directly on the Program Case Action Item (mvn__PJN_Program_Case_Action_Item__mdt) custom metadata type while custom action items can be created, modified, and deleted by users on the Action Items LWC. For both types of action items, users can directly reorder and check off (i.e., mark them as complete) in the Action Items LWC. When a user checks off an action item, the Is Complete (mvn__PJN_Is_Complete__c) field on the related Action Item record will be updated to equal true. Admin users can also enable and/or restrict users from creating and reordering action items on the Action Items LWC with the Feature Activation (mvn__Feature_Activation__mdt) custom metadata type.