Skip to main content

Guestline Rezlynx: Overbooking - PMS and CRS Logs

You can monitor and track all changes made to overbooking configuration settings through the comprehensive logging system in a few simple steps.

Xanthe Jackson avatar
Written by Xanthe Jackson
Updated over a week ago

The Overbooking Logs provide a complete audit trail of all configuration changes, showing who made them and when, while also offering historical data and troubleshooting support.


Accessing Overbooking Logs

You can monitor and track all changes made to overbooking configuration settings using the overbooking logs.

To access overbooking logs, follow the steps below:

  1. Navigate to Help, Logs, then Overbooking Configuration.

  2. Set the From and To dates as required.

  3. Additional filters can be used to refine the results, including:

    • Event Type: Filter by desired event, for example Change to Room Type Overbooking values

    • Operator: Filter by specific operator code.

  4. Click Refresh to see the search results.

The results grid will display all changes that match your selected filters, showing the following columns: timestamp, event type, operator, and details of the change.


Event Types Explained

The overbooking logs capture four distinct types of events:

  • Overbooking Limits Value Updated
    Purpose: Records specific values entered in Ini Settings Overbooking Limits.
    What it tracks: Changes to numerical limit values for each room type.

  • Overbooking Limits Restriction Updated
    Purpose: Records when values are added or removed in Ini Settings Overbooking Limits.
    What it tracks: Addition or removal of overbooking restrictions for each room type.

  • Room Overbooking Config Updated
    Purpose: Records room type values in the Overbooking configuration grid.
    What it tracks: Room-specific overbooking values that are entered or removed within the configuration grid.

  • House Overbooking Config Updated
    Purpose: Records House/Overall values in the Overbooking configuration grid.
    What it tracks: Property-wide overbooking values that are entered or removed within the configuration grid.

You can learn more about specific overbooking actions using our guides:

Did this answer your question?