The event is at the center of the MICE functionality of Clock PMS+ and stores the main details about it. All other elements(blocks, caterings, meeting room bookings, etc) are connected to the event.
Fields
Field name | Type | Description/Notes |
id | INTEGER | Unique identifier of the event across the entire Clock PMS+ ecosystem* |
account_id | INTEGER | Identification of the account owning the record. Reference to accounts table* |
created_at | TIMESTAMP | Time created (Date and time in UTC)* |
updated_at | TIMESTAMP | Time lastly updated (Date and time in UTC)* |
user_created | STRING | Name of the Clock PMS+ user created the event* |
user_updated | STRING | Name of the Clock PMS+ user updated the event* |
number | STRING | User defined number of the event. Please note the numbers are not unique and may be duplicated. The number may contain prefix and suffix* |
name | STRING | Name of the event* |
company_id | INTEGER | Unique ID of the company associated with the event. Reference to Companies table* |
agent_id | INTEGER | Unique ID of the agent associated with the event. Reference to Companies table |
contact_person_id | INTEGER | ID of guest associated with the company profile. The ID is a relations to guests table. |
arrival | DATE | Start date (YYYY-MM-DD) of the event* |
departure | DATE | End date (YYYY-MM-DD) of the event* |
checkin_status | STRING | Event check-in status can be: 'expected', 'checked_in', 'checked_out', 'canceled' or 'no_show'. Events having the last two statuses ('canceled' or 'no_show') are considered not to be valid.* |
guarantee_status | STRING | Event guarantee status can be: 'guaranteed', 'non_guaranteed', 'allotment' or 'optional'. It is important to know that Blocks for events of statuses 'allotment' or 'optional' are not included in the hotel occupancy.* |
assigned_to_user | STRING | Name of the Clock PMS+ user responsible for the event. |
assigned_to_department | STRING | Name of the Clock PMS+ department responsible for the event. |
report_segment_id | INTEGER | Relation to report_segments table which is holding the segmentation information for the booking* |
block_cut_off_days | INTEGER | How many days earlier the blocked rooms to be automatically released. |
block_expire_date | DATE | The date on which blocked rooms to be released for sale. In contrast to Cut-off days, where only a part of the block is released, through Expiry date the whole block (the whole block period) is released |
deposit_amount_cents | INTEGER | If a deposit amount is set for this Event in cents (10 EUR = 1000 cents) |
deposit_amount_currency | STRING | Currency of the deposit amount ISO 4217 currency codes |
client_requirements_collected | BOOLEAN | true / false if the requirements of the customers were collected* |
note | STRING | Event notes |
links | STRING | Links to additional information about the event |
color | STRING | color may have one of the following values:
|
tags | STRING | The tag associated with the event |
* Field will have value for every record