Here’s what new and improved in v4.37…

Quickly Process Multiple Booking Requests

Until now, booking requests could only be approved one by one, or every request could be “bulk” approved at once. For v4.37, we’ve introduced selective approval which saves time by allowing multiple booking requests to be approved in a single one action – Read more…

Custom Field Improvements

Custom “Text Areas” can now have a height set, and be set to be resizable too. Additionally, custom file upload fields can be configured to either view or save/download attached files – Read more…

Invoicing Improvements

Updating an invoice’s internal notes is now recorded in the Recent Activity audit log. Also, manual quotation payments for tentative bookings can now also update the booking’s type – Read more…

Better Support for “Shared” email addresses

If you have individuals using the public booking/request features of your MIDAS system, and they’re making bookings/requests on behalf of multiple organizations but using their personal email address for each, then v4.37 has improved support for such “shared” email addresses – Read more…

Day Notes can now appear on booking printouts

Notes that are attached to specific calendar dates in your booking system can now be set to be included on booking printouts – Read more…

Deprecating some outdated settings

We’ve removed the “SSL Access” setting, and changed the “Allowed IP Range” setting to now only be available in cloud-hosted edition – Read more…

Other Improvements

This latest version of MIDAS also includes stability and performance improvements, theme/UI updates, and fixes for several issues that have been detected or reported since the previous release (v4.36) – View the complete v4.37 changelog….

How To Get MIDAS v4.37…

The post MIDAS v4.37 Out Now! appeared first on MIDAS - Room Booking System | Blog.

These notes are then shown to all users who navigate to that date (or to a date within that range).

This can be used to remind other users of special dates, when your closed for public holidays, or other activities or notable events to be aware of on certain dates.

Dates with notes associated with them are also indicated on the Booking Availability screen where they can be quickly viewed before new bookings are added.

MIDAS v4.37 introduces a new setting which now also allows you to include date notes on your booking print outs.

This new setting may be found under MIDAS Admin Options → Manage MIDAS → Print → Include Date Notes on printouts.

The post Include Date Notes on booking print outs appeared first on MIDAS - Room Booking System | Blog.

As this can be done without requiring a login or a user account. When making a “public” booking/request, the person simply needs to enter their details. This will typically include their name and contact email address.

When a public web booking/request is made, MIDAS checks the email address that’s been entered against its existing client database.

If a single matching client with the same email address already exists in the client database, MIDAS will associate the booking/request with that existing client.

This negates the need for a person to have to re-enter all their information (i.e. address, phone number, etc) each time they make a web booking or request.

MIDAS can also be configured to allow individuals to update their information each time they make a web booking or request.

Multiple clients with the same email address

But what if there is more than one existing client with the same email address as the person making the web booking / request?

In these instances, MIDAS will not only compare the email address given, but also the client and organization names provided.

If there is a single exact match based on this additional information, MIDAS will associated the booking/request with the one matching client.

Again, MIDAS can be configured to update the existing client record at time of web booking / request with new details supplied by the individual.

The problem

There is however an “edge case” where the above options don’t quite go far enough.

Take for example an individual who uses their personal email address to make web bookings or requests for multiple different organizations they’re associated with.

That’s no problem if there are existing client records for the client for each of their organizations. But it becomes an issue if this is a brand new client. It’s also an issue if this is a person with just a single existing client record under one of their organizations.

Here’s an example to illustrate:

Let’s say Jeff is associated with two organizations – let’s call them “A” and “B”.

Let’s also assume that Jeff is a brand new client. There is therefore currently no client record with the same email address existing in your MIDAS system.

Jeff makes a booking request using his personal email address on behalf of organization “A”. A new client record is created for Jeff using this information.

A short while later, Jeff makes another booking request. He uses his personal email address again, but this time he’d like to make a request for organization “B”.

When Jeff makes his second request, MIDAS will see that there is already a single client in its database matching Jeff’s email address. One of two things will then happen, depending whether the “Allow client record updates” setting has been enabled in MIDAS.

If the “Allow client record updates” option is disabled, MIDAS will reuse Jeff’s original details (i.e. organization “A”). This will result in both his booking requests being for organization A.

If the “Allow client record updates” option is enabled, MIDAS will update Jeff’s original details (i.e. to become organization “B”). This will result in both his booking requests being for organization B.

…but that’s not what we want! We want his first request to be for organization A, and his second for organization B.

The solution

Instances of someone making web bookings / requests on behalf of multiple organizations using the same email address are uncommon. But we still wanted to better accommodate this scenario.

So for MIDAS v4.37 we’ve introduced a new “Account for multiple clients/organizations sharing the same email address” setting.

Enabling this setting will automatically create additional client records for each client/organization variant using the same email address.

The result – in our illustrative example above – would be that Jeff can make booking requests for either organization A or B (or even a future organization C) using his personal email address without issue.

The post Better support for “shared” email addresses appeared first on MIDAS - Room Booking System | Blog.

For MIDAS v4.37, we’ve made a couple of improvements based on customer feedback.

Manual quotation payments for tentative bookings can now update the booking’s type

“Tentative” bookings were first introduced in MIDAS v4.14 in 2016. Bookings of this type are automatically removed from the system if they’ve not ‘confirmed’ within a specified time frame or by a certain date/time.

In 2023, we also introduced a “quotation” feature. Used in conjunction with tentative bookings, you could generate quotations for clients when making tentative bookings for them.

If the client accepts and pays their quotation online, their ‘tentative’ bookings automatically convert to regular ‘confirmed’ bookings.

Of course, there may be instances when a client wishes to accept a quotation but pays ‘offline’ – perhaps over the phone or in person.

MIDAS can deal with ‘offline’ payments by allowing administrators to manually update quotations or invoices to reflect that a payment has been made against them.

Starting with MIDAS v4.37, if ‘manual’ payment is made for a quotation for a tentative booking, this can now update the associated bookings and make them ‘confirmed’.

Previously, this functionality was only available when an ‘online’ payment was made for a quotation.

Updating an invoice’s internal notes is now recorded in the Recent Activity Log

We appreciate that keeping an accurate audit trail is essential. The ‘Recent Activity Log’ in our software logs all user actions with date and time stamps. This useful log (which can also be downloaded) allows administrators to monitor how their booking system is being used.

Whenever an invoice’s status is updated, these actions are recorded to the audit log.

Each invoice can also have ‘internal notes‘ added to them. These notes are not visible to the recipient of the invoice, but are visible to administrators when viewing an invoice.

Until now, the action of updating internal notes for an invoice was not recorded to the ‘Recent Activity Log’ itself.

We’ve addressed this for v4.37. Whenever an administrator makes or updates the internal notes for an invoice, quotation, or credit note, this activity is noted in the recent activity log.

The post A couple of invoicing improvements for v4.37 appeared first on MIDAS - Room Booking System | Blog.

Once a booking request is submitted, the manager(s) of the request facility are notified. A manager can then then quickly approve or reject the booking request in MIDAS with just a few clicks.

In MIDAS v4.14 in December 2016 we introduced the option to allow a manager to “bulk” approve or reject all outstanding requests with just a single click.

This saved time in instances where there were numerous booking requests which all required approval or rejection.

To be able to bulk approve a number of booking requests, a setting was made available. This instructed MIDAS as to the order in which it should approve requests when approving them in bulk.

The “Bulk Approval Order” setting has the following options:

• Earliest Requested First – Booking requests will be approved in the order in which they were received. The earliest request received will be approved first.
• Latest Requested First – Booking requests will be approved in the reverse order in which they were received. The most recently received request will be approved first.
• Earliest Commencing First – Booking requests will be approved in the order in which the requested booking would start. Requests for the soonest start times will be approved first.
• Latest Commencing First – Booking requests will be approved in the reverse order in which the requested booking would start. Requests for the furthest away start times will be approved first.

For MIDAS v4.37 we’re giving managers even greater control when it comes to processing multiple booking requests.

In addition to be able to approve or reject one booking request at a time, or “bulk” approve/reject ALL requests at the same time, you can now also selectively approve/reject multiple requests.

On the Pending Booking Requests screen there’s now a checkbox alongside each request that’s awaiting processing.

A manager can use these tick boxes to select multiple requests and then click the “Approve Selected” or “Reject Selected” buttons at the bottom of the screen to process the selected requests accordingly.

If no requests are selected, the “Approve Selected” and “Reject Selected” buttons change. They then become the familiar “Approve All” and “Reject All” options which if used process all requests in the queue.

The post Selectively process multiple booking requests appeared first on MIDAS - Room Booking System | Blog.

For MIDAS v4.37, we’re making improvements to a couple of the ‘custom’ fields you can add to your scheduling system.

Custom “Text Area” fields can have a height set and can be resizable

Sometimes a single-line input field may not be sufficient to capture the amount of information you desire. In such instances, MIDAS allows you to alternatively create a multi-line “Text Area” input field.

Until now, creating a custom Text Area field would display a text input field with a relatively small height. Whilst its contents would be scrollable, the field would typically only show 2-3 lines of text at a time.

Now when creating (or editing) a custom Text Area field, you’ll have more control! You’ll be able to specify the number of rows that should be displayed at any given time on the field.

So if you anticipate that your custom field is only going to hold a couple of lines of text, you can set the number of rows to display low. But, if you expect your custom field to capture dozens of lines of text, you can increase the number of rows shown.

Furthermore, you can also set a custom Text Area field to be “Resizable”. When a Text Area field is set as resizable, a user will be able to drag the bottom of the custom Text Area field down to allow the display of more lines of text at once.

Custom file uploads can be set to either view or save/download the file when clicked

The custom “File Upload” field was first introduced in MIDAS v4.07. If utilized, this allows a document or file to be uploaded and attached to a booking or client record.

When we implemented this custom field type in 2014, we configured MIDAS to ‘hint’ to an end-users user’s browser that an uploaded and attached file should be ‘downloaded’ to the user’s device when clicked.

In those days, it wasn’t common place for web browsers to be able to open a variety of file types. There was even a time when browsers would struggle to open and correctly display PDF files.

These days, web browsers can open and display a wide range of document/file types.

For v4.37, we’ve provided administrators with the option to allow MIDAS to ‘hint’ to user’s browsers whether an custom file upload should be either ‘downloaded’ to the user’s device when clicked, or ‘opened/displayed’ in a new window/tab instead.

So if you’re attaching PDF files to bookings, for instance, you can now instruct browsers to display these files in your browser instead of prompting you to download them to your device.

Please note that MIDAS only provides ‘hints’ to user’s browsers as to whether to view or download an attached file. It’s down to individual browsers as to whether they respect these hints and how they process the attached files.

The post Custom Field Improvements in v4.37 appeared first on MIDAS - Room Booking System | Blog.

In this post, we’ll outline what’s changing and explain the reasons behind the decision to remove these options.

“SSL Access” setting has been removed

In the early days of the World Wide Web, you connected to websites over “http”.

“http” connections were not secure and could be intercepted. So along came “https”, which allowed visitors to connect to websites over encrypted Secure Socket Layer – or SSL – connections.

However, adoption of “https” was initially slow by the majority of the World Wide Web. Primarily, this was due to SSL certificates being very expensive. Large financial institutions were naturally quick to jump on https. However, the price of SSL certificates put securing websites with https out of reach of the average webmaster. Especially when the cost to renew them every 1-2 years was factored in.

Now, as you may know, we’ve been developing our web based MIDAS room booking software for nearly 20 years now! When we first began to offer a “cloud hosted” booking system to customers (way back in 2007), SSL/https use around the web was not wide spread, and was expensive to implement.

Initially in 2007, we offered our cloud-hosted customers the option of being able to access their hosted MIDAS system over secure https. This was available via an optional (paid) addon for their scheduling system.

By June 2011, we’d recognized the importance and benefit of secure SSL connections for all our customers to their MIDAS systems. We therefore introduced better support for secure SSL connections with MIDAS v3.13.

As part of this, we added a new “SSL Access” setting to v3.13. This allowed administrators to control whether insecure http and/or secure https connections would be permitted to their MIDAS system.

In August 2012, we then took the further decision to include an SSL Certificate to enable secure connections for all our existing and future cloud hosted customers. At the same time, we enforced https connections to all hosted MIDAS system.

Consequently, the “SSL Access” option first introduced in MIDAS v3.13 became redundant for our cloud-hosted customers. Since 2015 and MIDAS v4.09, this option has no longer been available in cloud-hosted editions of our booking system.

In the following years, gradually the cost of SSL certificates reduced. Then in 2016, along came a game-changing service called “Let’s Encrypt“. Let’s Encrypt offered FREE SSL certificates for all. This finally allowed every webmaster the ability to “secure” visitor connections to their websites at zero cost.

In May 2018 we migrated all our cloud-hosted customer’s SSL certificates from expensive GlobalSign certificates to ones issued for free by Let’s Encrypt instead.

Now, in 2024, SSL/https certificates are the norm – in fact, all modern web browsers now alert you if you attempt to visit an insecure website via http.

So whilst we removed the “SSL Access” settings in cloud-hosted MIDAS systems back in 2015, we’re now also removing these settings for self-hosted customers starting with MIDAS v4.37.

“Allowed IP Range” setting has been removed (self hosted editions only)

The “Allowed IP Range” setting is one of the earliest security settings we provided in our room booking system. In fact, it was first introduced in v1.35 back in August 2007.

The setting allows an administrator to restrict access to their MIDAS system to an IP address or range.

This can be useful if a MIDAS system is hosted on a public-facing web server, which potentially could be accessed by anyone worldwide. The “Allowed IP Range” setting can be used to restrict access to users in your own country, organization, or to just you!

However, one of the limitations of this setting is that it only supports ipv4 address, and not ipv6 addresses.

Also, in the years since this setting was first introduced, other security and firewall products are available which provide greater control over access to websites, apps, and servers.

Therefore, starting with MIDAS v4.37, we have removed the “Allowed IP Range” setting in self-hosted editions.

If you’re a self-hosted customer and wish to restrict access to your MIDAS system by IP address you should consider other options to achieve this.

For instance, on Apache servers, you can easily allow/deny access by ip address/range in your httpd.conf or .htaccess files. For more information, please see Apache’s guidance on access control.

“Do Not Track (dnt)” has been superseded by “Global Privacy Control”

“Do Not Track” – or ‘dnt’ for short – was an official HTTP header first proposed in 2009. It was intended to allow user to opt-out of tracking by websites.

By 2011, all major web browsers had implemented support for the proposed “Do Not Track” features.

In 2017, with the release of MIDAS v4.16, we included an “Honor user’s Do Not Track preference” setting.

If enabled (and if an end-user had also enabled the “Do Not Track” feature in their browser), MIDAS would not log the user’s IP address in the Recent Activity Log.

However, globally, recognition and support of the “Do Not Track” HTTP header by websites was poor. So much so that in January 2019, the “Do No Track” HTTP header was officially deprecated. A month later, Apple removed DNT support from their Safari browser.

Whilst some other browsers still continue to offer a “Do Not Track” setting, it has since been supersede by a new “Global Privacy Control” – or GPC – header.

At time of writing, Global Privacy Control is still classed as an “experimental” and “non standard” technology, and it’s behaviour may change in the future.

But for MIDAS v4.37, we’ll support both DNT and GPC features. The “Honor user’s Do Not Track preference” setting will be renamed to “Honor user’s privacy preferences” to reflect this.

It’s likely that in a future update we’ll fully drop support the deprecated “DNT” header. At time of writing though, as some browsers still support it, we’ll continue to support it too.

The post Deprecating some outdated settings appeared first on MIDAS - Room Booking System | Blog.