List of terms with an explanation
| Table of Contents | ||||
|---|---|---|---|---|
|
Task
A notification will be sent based on the action and conditions that are set up in a task.
A task is created in 3 steps:
- Task: determine what to send
- Action: determine to whom to send
- Conditions: determine when to send
Context
The context determines where to observe data changes.
Default context:
- Reservation
- Reserved Items
- Payment
- Invoice
...
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.
Task
A notification will be sent based on the action and conditions that are set up in a task.
Trigger
A trigger is a criterion for an event that determines when the notification will be sent to the appropriate receiver.
...
- Manual (notification triggered manually)
- Change (notification triggered on change)
- Periodical (notifications triggered periodically on time)
...
Manual: send out a bulk notification for a one-off event
- Examples: In case the customer needs to be informed that the Arrival time at the booked Resort changed, Name of Resort changed, etc.
Change: send out a notification when a certain values changevalue changes
- Examples: Booking confirmation, Cancellation confirmation, Bill updated etc.
Periodical: send out a notification for repeating recurring events
- Examples: Pre-arrival information, Welcome home email, Reminders, etc.
...