The table below provides a comprehensive overview of all fields and relationships for the Appointment object in Maica. Please refer to the table below for detailed information.
Click here to view and download the complete Appointment Schema.
Validation Rules
The list below outlines the Validation Rules applied to the Appointment Object in Maica.
Please refer to the list below for more detailed information on each Validation Rule.
End Time Cannot Be Before Start Time
Ensures that the End Time cannot be set prior to the Start Time.
The list below outlines the Flows applied to the Appointment Object in Maica.
Please refer to the list below for more detailed information on each Flow.
Appointment Geocoding
This flow is designed to geocode the address of an appointment upon creation or update of the appointment record.
Flow Summary
This flow geocodes the address of an appointment and updates the appointment record with the latitude and longitude by:
Triggering on the creation or update of an appointment record.
Geocoding the address fields using an Apex action.
Checking for errors in the geocoding process.
Updating the appointment record with the geocoded latitude and longitude if no errors occur.
Flow Description
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.
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.
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.
Update Appointment (Record Update):
Updates the appointment record with the latitude and longitude values obtained from the geocoding process.
Ends the flow.
Trigger Handlers
The table below outlines the Trigger Handlers applied to the Appointment Object in Maica and their Load Order.
Please refer to the list below for more detailed information on each Trigger Handler.
Appointment Time Sheet
This trigger is designed to manage the timesheets for appointments in Maica. The outcome is accurate and reliable timesheet data for all appointments, ensuring proper time management and reporting.
Execution, Logic & Outcome
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
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).
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.
Appointment Status
This trigger is designed to manage the status updates for appointments in Maica. The outcome is accurate and reliable status tracking for all appointments, ensuring proper management and communication.
Execution, Logic & Outcome
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
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).
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.
Appointment Rollup Participants
This trigger is designed to manage the rollup of participants for appointments in Maica.
Execution, Logic & Outcome
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
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).
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.
Appointment Geocoding
This trigger is designed to manage the geocoding of appointments in Maica, maintaining accurate geographical data.
Execution, Logic & Outcome
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
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).
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.
Appointment Delivery Activities
This trigger is designed to manage the delivery activities for appointments in Maica.
Execution, Logic & Outcome
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
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).
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.
Validation Rule Detail
Validation Rule Detail
Validation Rule Detail
Flow Detail
Trigger Handler
Load Order
Detail
Detail
Detail
Detail
Detail
Rule Name
VAL_APPOINTMENT_0001
Error Message
VAL_0001: The End Time cannot be prior to the Start Time.
Error Location
Top of Page
Rule Name
VAL_APPOINTMENT_0002
Error Message
VAL_0002: The checkout date/time must be greater than the checkin date/time.
Error Location
Top of Page
Rule Name
VAL_APPOINTMENT_0003
Error Message
VAL_0003: A Cancellation Date must be entered if a Cancellation Reason is selected.
