Over the festive period, we released a new update to MIDAS, which we’re pleased to share details of with you here on our blog.

Highlights of MIDAS v4.29 include:

• New: Two additional “Can Make Bookings” user permission options to restrict the user to only be able to book/request for themselves
• New: “Mark as read” option for messages, reminders, and watch notifications in the Notification Center
• New: Support for specifying a Reply-To email header
• Improved: Additional Date Format settings to include named day of the week
• Improved: Additional logout inactivity settings (5, 15, and 20 minute options)
• Improved: Quickly reply to internal messages
• Improved: Printing a monthly calendar no longer displays scrollbars in date cells
• Improved: Display of multiple lengthy resource category names
• Improved: Loading indicator shown during more navigation actions
• Improved: Warning if trying to create an additional database with the same name as an existing database
• Improved: Auto approved booking requests now logged in Recent Activity Log
• Optimization: Code optimization
• Optimization: Database query optimization
• Fixed: Cumulative roll-up of various fixes for issues discovered since v4.28

How To Get MIDAS v4.29…

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

MIDAS is no exception, and an extensive range of email settings and options are available in the software. Administrative users may configure these via MIDAS Admin Options → Manage MIDAS → Email.

One of the available email settings allows you to have email notifications sent from your MIDAS system to be sent from a particular email address.

Typically, for automated emails that you don’t require a response to, you may specify a “no-reply” style address.

However, what if you want to provide a way for your customers to contact you should they have any queries?

Well, you could use a real email address instead of a no-reply “black hole” inbox which isn’t monitored.

Or, from MIDAS v4.29 onwards, you could instead specify a “Reply To” email address. This can be different from the address that emails from your MIDAS system are sent from.

In the above example screenshot, all email sent from the MIDAS system will be sent as though it originated from the address “noreply@example.com”.

However, if a recipient of an email from this MIDAS system hits “Reply”, they’ll be composing a message that will be sent to “roomhire@example.com” (instead of “noreply@example.com”.

This new setting adds a standard “Reply-To” header to all outgoing email from your MIDAS system.

More information on the various email configuration options and settings in MIDAS may be found in the documentation.

The post Specify an alternate “reply to” email address appeared first on MIDAS - Room Booking System | Blog.

In MIDAS v4.28 we introduced a new “Notification Center“. The Notification Center allows users to view messages from other users, booking and custom reminders, and Watch notifications.

Notifications each have their own expiration time, after which they are automatically removed from a user’s Notification Center. Users could also manually remove a notification at any time.

For MIDAS v4.29 we’re also giving users the option to mark notifications as having been “read”.

Read notifications will still be present in the user’s Notification Center until they expire or are manually removed. However, unread notifications will be highlighted, whereas read notifications won’t be.

Also, if the user has opted to be shown their notifications each time they log in, this popup will now only show them their unread notifications. So the new “mark as read” option will help keep clutter to a minimum. It will only show notifications the user hasn’t yet seen and acknowledged on the notification pop-up after login.

Users will of course still be able to see all their notifications – both read and unread – via the Notification Center icon.

The post Mark notifications as “Read” appeared first on MIDAS - Room Booking System | Blog.

For MIDAS v4.29, we’re expanding the range of options available to administrators when it comes to assigning user permissions.

MIDAS already includes an extensive range of permissions which can be assigned on a per-user basis. One of these permissions is the “Can Make Bookings” permission. This setting controls whether a given user account can make bookings, or just booking “requests”, or neither.

Following customer feedback, we’re adding a couple of additional options to this particular user permission.

Now administrators can restrict user accounts to only be able to book/request for themselves.

Prior to this, a user with permissions to make bookings/requests could select a client on their Add Bookings screen that the booking or request was to be for.

Now, if the “Can Make Bookings” permission is set to “Yes (For self only)”, the user will only be able to make bookings for themselves. They will not be able to make bookings for any arbitrary client in the system.

Similarly, the “Requests Only (For self only)” option works the same, but only allows the user to make booking requests for themselves.

The post Restrict users to “self-booking” only appeared first on MIDAS - Room Booking System | Blog.