LogoLogo
Maica's Homepage
Admin Guide
Admin Guide
  • Welcome to Maica Administration
  • Getting Started
    • Check your Salesforce Hosting
    • Licence Agreement
    • The Maica Release Process
    • Find your Maica Edition
    • The Implementation Process
  • Data
    • Data Objects
      • Agreement Item
      • Appointment
      • Availability
      • Booking Item
      • Checklist
      • Client Note
      • Connection
      • Contact
      • Delivery Activity
      • Funding
      • Funding Item
      • Invoice
      • Invoice Line Item
      • Location
      • Log
      • Payment Request
      • Preference
      • Price List
      • Price List Entry
      • Resource
      • Resource Participant
      • Service Agreement
      • Service Agreement Leave
      • Service Agreement Statement
      • Service Booking
      • Shift
      • Support Category
      • Support Item
      • Timesheet
      • Timesheet Entry
      • Unavailability
    • Permission Sets
    • Reference Data
      • Reference Data Template
      • Import Template
    • Data Import Utility
      • NDIS Support Catalogue
      • Data Import Flows
  • System Processes
    • Billing Invoice Generation
    • Timesheet Generation
    • Recurring Schedules
    • Travel Claiming and Expenses
    • Public Holiday Configuration
    • Configuring Maica Components
      • Appointment Services
      • Support Items
      • Support Categories
      • Overnight and 24 Hour Availability
  • Enable Maica Actions
  • Scheduled Jobs
  • Maica Timezone Management
  • Integrations
    • Create a Site
    • Xero Integration
      • Support Item Configuration
    • Stripe Integration
    • NDIS Notifications
  • Settings
    • Renewal Management
    • Claim Management
      • NDIS
        • Handle BPR Results & Remittance Files
        • BPR File Import Flows
      • Aged Care
    • Invoice Management
    • Support Item Management
    • Integration Management
      • NDIS Integration
      • Stripe Integration
      • Xero Integration
    • Connections Management
      • General Settings
      • Reciprocal Settings
    • General Settings
    • Planner Management
    • Rostering Management
    • Service Management
    • Timesheet Management
    • Validation Management
    • Travel Management
    • Billing Management
    • Maps Management
    • Participant Notes
Powered by GitBook

Further Maica Resources

  • Homepage
  • Features
  • FAQs
On this page
  • Fields & Relationships
  • Automation
  • Flows
  • Booking 90 Days Before Expiration Notification
  • Booking Utilisation Change Notification

Was this helpful?

Export as PDF
  1. Data
  2. Data Objects

Service Booking

The Service Booking object in Maica represents a PRODA Service Booking (Plan) for a given Participant.

PreviousService Agreement StatementNextShift

Last updated 9 months ago

Was this helpful?

Fields & Relationships

The table below provides a comprehensive overview of all fields and relationships for the Service Booking object in Maica. Please refer to the table below for detailed information.

Automation

Flows

The list below outlines the Flows applied to the Service Booking Object in Maica.

Please refer to the list below for more detailed information on each Flow.

Booking 90 Days Before Expiration Notification

This flow is designed to send an email notification 90 days before the expiration of a service booking.

Flow Detail

Flow Label

Maica - Booking 90 Days Before Expiration Notification

API Name

maica__Booking_90_Days_Before_Expiration_Notification

Type

Autolaunched Flow

Flow Summary

This flow sends an email notification 90 days before the expiration of a service booking by:

  • Detecting changes to service booking records and scheduling the flow to run 90 days before the end date.

  • Checking if the email template is set and if the end date is in the future.

  • Determining the email recipient based on the email setting.

  • Sending the email notification to the determined recipient.

Flow Description
  1. Start (Record-Triggered Flow):

    • The flow is initiated upon the creation or update of a service booking record.

    • Scheduled to run 90 days before the service booking's end date.

    • Proceeds to a placeholder assignment to fix packaging issues.

  2. Is Template in Email Setting Null And End Date in Future? (Decision):

    • Checks if the email template is set and if the end date of the service booking is in the future.

    • If the conditions are met, proceeds to determine the email recipient.

  3. To Whom Should This Message Be Delivered? (Decision):

    • Determines the recipient of the email based on the email setting:

      • If the recipient is the current participant owner, sets the user ID to the participant owner ID and proceeds to send the email.

      • If the recipient is a specific user and the user ID is set in the email setting, sets the user ID to the specified user ID and proceeds to send the email.

  4. Set Service Booking Participant Owner Id (Assignment):

    • Sets the user ID to send the email to the participant's owner ID.

    • Proceeds to send the email.

  5. Set User Id (Assignment):

    • Sets the user ID to send the email to the user ID specified in the email setting.

    • Proceeds to send the email.

  6. Send Email (Apex Action):

    • Calls the SendEmailInvocable Apex action to send the email.

    • Passes the email template, sender's email address, and recipient's user ID as input parameters.

    • Ends the flow.

Booking Utilisation Change Notification

This flow is designed to send an email notification when the utilisation of a service booking crosses a specified threshold.

Flow Detail

Flow Label

Maica - Booking Utilisation Change Notification

API Name

maica__Booking_Utilisation_Change_Notification

Type

Autolaunched Flow

Flow Summary

This flow sends an email notification when the utilisation of a service booking crosses a specified threshold by:

  • Detecting changes to service booking records.

  • Checking if the email template is set.

  • Determining whether the email notification should be sent based on the utilisation thresholds.

  • Identifying the email recipient based on the email settings.

  • Sending the email notification to the determined recipient.

Flow Description
  1. Start (Record-Triggered Flow):

    • The flow is triggered upon the creation or update of a service booking record.

    • The flow runs asynchronously after the record is saved.

    • It proceeds to check if the email template is set.

  2. Is Template in Email Setting Null? (Decision):

    • Checks if the email template specified in the email settings is not null.

    • If the template is set, proceeds to check if the email notification should be sent.

  3. Should The Email Notification Be Sent? (Decision):

    • Determines whether the email notification should be sent based on the following conditions:

      • The current utilisation is not null.

      • The previous utilisation is not null.

      • The previous utilisation is less than the threshold specified in the email setting.

      • The current utilisation is greater than the threshold specified in the email setting.

    • If all conditions are met, proceeds to determine the email recipient.

  4. To Whom Should This Message Be Delivered? (Decision):

    • Determines the recipient of the email based on the email setting:

      • If the recipient is the current participant owner, sets the user ID to the participant owner ID.

      • If the recipient is a specific user and the user ID is set in the email setting, sets the user ID to the specified user ID.

    • Proceeds to send the email.

  5. Set Service Booking Participant Owner Id (Assignment):

    • Sets the user ID to send the email to the participant's owner ID.

    • Proceeds to send the email.

  6. Set User Id (Assignment):

    • Sets the user ID to send the email to the user ID specified in the email setting.

    • Proceeds to send the email.

  7. Send Email (Apex Action):

    • Calls the SendEmailInvocable Apex action to send the email.

    • Passes the email template, sender's email address, and recipient's user ID as input parameters.

    • Ends the flow.

  8. Handle Error (Assignment):

    • If an error occurs during the process, assigns the error message to the FlowFaultMessage variable.

Click to view and download the complete Service Booking Schema.

here
Service Booking Schema