Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

https://app.diagrams.net/#G1AHNzaFTLtvEPNoDWS78Btmo61dPGj_bV
https://lucid.app/lucidchart/d8b21abf-9c7e-475f-889d-205a887e7fba/edit?invitationId=inv_70d39142-5695-49a1-903c-e3c58c9d84a5&page=XVOBKPu7aP4u7#

Object

Standard/Custom

Description

Reservation

Custom

Our main object, this represents an event / booking / reservation between two dates / times

Contact

Standard

The standard Contact object

Account

Standard

The standard Account object

Reservation Contact

Custom

Junction between Contact and Reservation, allowing you to add multiple “attendees” to a reservation

Reservation Type

Custom

A Reservation Type determines the type of the Reservation. Determines which fields are displayed on the form and which records are related to this Reservation Type

Reservation Status

Custom

A Reservation Status determines in which status a Reservation is (allowing you to configure the colours of the reservation on the calendars and add your own logic when a reservation status is selected)

Conflict

Custom

When a soft conflict occurs a Conflict record is stored in this object, explaining why the Reservation conflicts (on availability, double booking or capacity)

Recurring Reservation

Custom

Holds details on the recurrence of a Reservation

Reservation Template

Custom

A templated reservation, holds specific details which can be activated as actual Reservations based on a pattern defined in the Schedule

Schedule

Custom

An abstract schedule / pattern (e.g. Monday to Friday) which can be activated to create actual Reservations

Staff

Custom

Our Staff object, which can relate to a Contact or a User

Additionally, and instead of the Staff object, you can use any existing Standard or Custom object in your org that holds this kind information. Think of a situation where you already have an object containing staff or employees (i.e. anyone you want to book). For this situation, please refer to this article.

Resource

Custom

A resource in the system (e.g. Room 1 or Building 1). Resources have a hierarchy that follow the Resource Type hierarchy.

Additionally, and instead of the Resource object, you can use any existing Standard or Custom object in your org that holds bookable information. Think of a situation where you already have an object containing cars, apartments, boats (i.e. anything you want to book). For this situation, please refer to this article.

Resource Type

Custom

The type of the Resource (such as building, room, etc.), Resource Types are created in a hierarchy

Availability

Custom

Determines the opening / closing times for the “bookable” Dimension (Resource, Staff or custom)

Service

Custom

A Service that can be booked within a Reservation

Service Type

Custom

A type of a Service (e.g. F&B or AV)

Service Availability

Custom

Determines when a Service can be used / bought in a Reservation

  • No labels