Context

Owned by Susan Smits
Last updated: May 09, 2019

The context determines where to observe data changes.


Default context:

  1. Reservation
  2. Reserved Items
  3. Payment
  4. Invoice


Reservation

Used for sending information that is specific for a reservation. For example the reservation confirmation, arrival information, ect.

Reserved Items

Used for sending information that is specific for an item (a.k.a. resource) booked in a reservation. This resource could also be an accommodation unit. Therefore this is mainly used for sending notifications to owners. For example, a reservation confirmation for a specific unit to the owner. This cannot be done with the Reservation context because a reservation can have two booked accommodation units. Therefore it's not clear on reservation level to which owner (it could be 2 different owners) the reservation confirmation should be sent. 

Payment

Used for sending information about payments. For example a payment confirmation to the guest.

Invoice (only used for business bookings)

Used for sending information specifically for invoices. Invoices should not be confused with payment terms which are automatically created for reservations. The user needs to manually create invoices in MXTS for a single reservation. The invoices entail static information about booked resources and the price. Even if the reservation changes the invoices stays static (i.e. will not change). After a change in the reservation, a new invoice needs to be manually created off-set the difference between the reservation total and the previously created invoices. This can be either a credit invoice or an additional normal invoices.