Appointment

1. Start (Record-Triggered Flow):

   • The flow is triggered upon the creation or update of an appointment record.

   • The flow runs asynchronously after the record is saved.

   • Proceeds to geocode the address.

2. Geocode the Address (Apex Action):

   • Calls the GeocodeAddressInvocableProc Apex action to geocode the address fields.

   • Passes the address fields and the record ID as input parameters.

   • Proceeds to the decision step to check for errors.

3. Error? (Decision):

   • Checks if there was an error during the geocoding process by evaluating the errorMessage from the Geocode_the_Address action.

   • No: If no error, proceeds to update the appointment.

   • Yes: If an error occurred, the flow ends without updating the appointment.

4. Update Appointment (Record Update):

   • Updates the appointment record with the latitude and longitude values obtained from the geocoding process.

   • Ends the flow.

Execution of Trigger Logic:

The trigger logic defined in the AppointmentTimeSheet_MDTM class is executed when the trigger conditions are met. The class contains the code that manages the timesheet process for appointments.

• Trigger Conditions:

  • When a new appointment (maica__Appointment__c) is created.

  • When an existing appointment is updated.

  • Any specific field changes that are monitored by the trigger (defined in the handler class).

Logic Explanation

1. Initialisation:

   • When an appointment record is created or updated, the trigger is initialised. The AppointmentTimeSheet_MDTM metadata type configuration is loaded, ensuring that the trigger is active (Active__c is true) and has the correct load order (Load_Order__c is 1.0).

2. Trigger Execution:

   • Upon initialisation, the trigger executes the logic defined in the AppointmentTimeSheet_MDTM class.

   • The class methods perform the following steps:

     • Validation: The appointment data is validated to ensure it is complete and accurate.

     • Timesheet Creation/Update: Based on the appointment details, timesheet entries are created or updated to reflect the time spent on the appointment.

     • Update: The appointment record is updated with the newly created or updated timesheet data.

Trigger Outcome:

Once executed, the trigger ensures that each appointment has its timesheet entries created or updated correctly, based on the logic defined in the handler class. This helps maintain accurate timesheet data for appointments.

Execution of Trigger Logic:

The trigger logic defined in the AppointmentStatus_MDTM class is executed when the trigger conditions are met. The class contains the code that manages the status updates for appointments.

• Trigger Conditions:

  • When a new appointment (maica__Appointment__c) is created.

  • When an existing appointment is updated.

  • Any specific field changes that are monitored by the trigger (defined in the handler class).

Logic Explanation

1. Initialisation:

   • When an appointment record is created or updated, the trigger is initialised. The AppointmentStatus_MDTM metadata type configuration is loaded, ensuring that the trigger is active (Active__c is true) and has the correct load order (Load_Order__c is 1.0).

2. Trigger Execution:

   • Upon initialisation, the trigger executes the logic defined in the AppointmentStatus_MDTM class.

   • The class methods perform the following steps:

     • Validation: The appointment data is validated to ensure it is complete and accurate.

     • Status Update: The appointment status is updated based on predefined criteria such as appointment type, time, and other relevant factors.

     • Notification: Relevant stakeholders are notified if necessary, ensuring that all parties are aware of the status changes.

Trigger Outcome:

Once executed, the trigger ensures that each appointment has its status updated correctly, based on the logic defined in the handler class. This helps maintain accurate status tracking for appointments.

Execution of Trigger Logic:

The trigger logic defined in the AppointmentRollupParticipants_MDTM class is executed when the trigger conditions are met. The class contains the code that manages the rollup of participants for appointments.

• Trigger Conditions:

  • When a new appointment (maica__Appointment__c) is created.

  • When an existing appointment is updated.

  • Any specific field changes that are monitored by the trigger (defined in the handler class).

Logic Explanation

1. Initialisation:

   • When an appointment record is created or updated, the trigger is initialised. The AppointmentRollupParticipants_MDTM metadata type configuration is loaded, ensuring that the trigger is active (Active__c is true) and has the correct load order (Load_Order__c is 3.0).

2. Trigger Execution:

   • Upon initialisation, the trigger executes the logic defined in the AppointmentRollupParticipants_MDTM class.

   • The class methods perform the following steps:

     • Validation: The participant data is validated to ensure it is complete and accurate.

     • Calculation: The total number of participants is calculated based on predefined criteria such as appointment type and participant status.

     • Update: The appointment record is updated with the newly calculated rolled-up participant data.

Trigger Outcome:

Once executed, the trigger ensures that each appointment has its participants rolled up correctly, according to the logic specified in the handler class. This helps maintain accurate participant data for appointments.

Execution of Trigger Logic:

The trigger logic defined in the AppointmentGeocode_MDTM class is executed when the trigger conditions are met. The class contains the code that manages the geocoding process for appointments.

• Trigger Conditions:

  • When a new appointment (maica__Appointment__c) is created.

  • When an existing appointment is updated.

  • Any specific field changes that are monitored by the trigger (defined in the handler class).

Logic Explanation

1. Initialisation:

   • When an appointment record is created or updated, the trigger is initialised. The AppointmentGeocode_MDTM metadata type configuration is loaded, ensuring that the trigger is active (Active__c is true) and has the correct load order (Load_Order__c is 4.0).

2. Trigger Execution:

   • Upon initialisation, the trigger executes the logic defined in the AppointmentGeocode_MDTM class.

   • The class methods perform the following steps:

     • Validation: The appointment address data is validated to ensure it is complete and accurate.

     • Geocoding: The validated address data is converted into geographical coordinates using geocoding services.

     • Update: The appointment record is updated with the newly obtained geographical coordinates.

Trigger Outcome:

Once executed, the trigger ensures that each appointment is geocoded correctly, according to the logic specified in the handler class. This helps maintain accurate geographical data for appointments.

Execution of Trigger Logic:

The trigger logic defined in the AppointmentDeliveryActivities_MDTM class is executed when the trigger conditions are met. The class contains the code that manages the delivery activities for appointments.

• Trigger Conditions:

  • When a new appointment (maica__Appointment__c) is created.

  • When an existing appointment is updated.

  • Any specific field changes that are monitored by the trigger (defined in the handler class).

Logic Explanation

1. Initialisation:

   • When an appointment record is created or updated, the trigger is initialised. The AppointmentDeliveryActivities_MDTM metadata type configuration is loaded, ensuring that the trigger is active (Active__c is true) and has the correct load order (Load_Order__c is 6.0).

2. Trigger Execution:

   • Upon initialisation, the trigger executes the logic defined in the AppointmentDeliveryActivities_MDTM class.

   • The class methods perform the following steps:

     • Validation: The appointment data is validated to ensure it is complete and accurate.

     • Activity Creation/Update: Based on the appointment details, delivery activities are created or updated to reflect the services or tasks associated with the appointment.

     • Update: The appointment record is updated with the newly created or updated delivery activity data.

Trigger Outcome:

Once executed, the trigger ensures that each appointment has its delivery activities created or updated correctly, according to the logic specified in the handler class. This helps maintain accurate delivery activity data for appointments.