RoomKeyPMS clients can now save their email configuration settings directly within their property’s RoomKeyPMS database!

This enhancement ensures that email settings are accessible to all Clerks logging into RoomKeyPMS, regardless of the workstation being used. By centralizing these settings at the database level, properties can significantly reduce the workload on their IT teams.

While the option to configure email settings via the computer registry remains available, storing settings in the database eliminates the need to configure or maintain settings across individual workstations or Windows user profiles. This streamlined approach saves time and simplifies overall system maintenance across the property.

For more information on configuring RoomKeyPMS to save email settings to the property/database, please refer to the following training documentation:  Saving Email Settings - Registry vs. Database

Existing properties can navigate directly to the section titled:  “Switching from Registry/Computer option to Property/DB option” for step-by-step guidance.

Payment failing due to quotes appearing in Guest Name => when attempting to post a payment using the RoomKeyPMS Payments powered by Fullsteam interface, users encountered the following error message:  “The request is invalid. An error has occurred.”  After further investigation and consultation with Fullsteam Support, it was determined that the issue was caused by the presence of quotation marks in the guest’s first name field (e.g., Robert "Bob").  The integration was unable to properly process these special characters, resulting in the failed payment request.

To resolve this issue, enhancements have been implemented within the RoomKeyPMS–Fullsteam integration. Moving forward, any quotation marks present in the guest’s first or last name will be automatically omitted before the data is transmitted to Fullsteam Payments. This ensures that payment transactions can be processed successfully without encountering this error.

Guest Credit Card not appearing as available when creating a New Reservation => when creating a reservation using an existing Guest Profile that had a credit card associated with it, the credit card was not initially available for selection to attach to the reservation.  Upon further investigation, it was determined that the associated credit card would not appear until a Room Type and Rate Plan were first selected on the General tab. Once these fields were populated, the stored credit card became available for selection.

To improve usability and ensure a more intuitive workflow, an update has been implemented. The system will now display any credit cards associated with the guest profile regardless of whether the Room Type and Rate Plan have been selected.  This enhancement ensures that users can access and apply stored payment methods at any point during the reservation creation process.

Date/Time to be printed on Room Availability Scan => based on frequent client requests, an enhancement has been made to the Room Availability Scan Report (located under Reports → Audits).  The report will now include the printed date and time, displayed in the bottom left-hand corner of the report.  This update provides improved visibility and tracking, allowing users to easily identify when the report was generated.

Restrict Negative Numbers from being entered into the Interface "Settle" box =>  within RoomKeyPMS, when navigating to Transactions → Authorized Transactions and selecting “Settle”, it was identified that users were able to enter a negative amount in the RoomKeyPMS Payments powered by Fullsteam interface field.  Entering a negative value created the impression that a refund would be processed. However, in practice, the transaction was still being settled, leading to potential discrepancies and confusion.  To prevent this issue moving forward, an update has been implemented to restrict the entry of negative amounts in this field. This ensures that only valid settlement values can be entered and helps maintain accurate transaction processing.

Error updating Microsoft OAuth 2.0 Token => a property reported encountering an error when attempting to update their Microsoft OAuth 2.0 token, which stated that the “code” parameter was not valid.  Upon investigation, the issue causing this error was identified and has now been resolved.  Properties should no longer encounter this error when updating their Microsoft OAuth 2.0 token, and the process should now complete successfully as expected.

Second Credit Card during Multi Folio Check Out was not being settled via Credit Card Interface => it was reported that when performing a Multi-Folio Checkout via the Check-Out screen, if both folios were being settled using different credit cards, the second credit card was not being processed through the RoomKeyPMS Payments powered by Fullsteam interface.  This issue has now been resolved. All credit cards used during a Multi-Folio Checkout will now be processed successfully, ensuring accurate and complete payment transactions.

Unable to Check In a No Show if Room Number is Assigned to Next Day Arrival => When attempting to Check-In a No Show Reservation, if an Arrival was expected in the same Room Number for the current day, the Clerk would encounter a “The following pre-assigned room is not available” warning.  The Clerk would then only be able to check-in the guest if they unassigned the Room Number from Today's Arrival.  This issue was tedious as it caused multiple extra steps in order to Check-In the guest reservation.  This issue has now been resolved and Clerks should no longer encounter this warning in this situation.  

Incorrect Zip Code assigned to Token on eRes Reservation => it was reported by a property that a Credit Card that was obtained via the eRes Online Booking Engine was failing due to the incorrect Zip Code being associated with the Credit Card.  Upon further investigation we found that we were sending the default Zip Code "11111" for eRes Reservation instead of the guests actual Zip Code.  This issue has now been fixed and the proper guest Zip/Postal Code will be associated with all eRes Reservation Credit Cards.

Do Not Move flag stuck on re-instated Reservation => it was reported that when a reservation with the Do Not Move flag was cancelled and then reinstated, the flag remained active. This prevented the clerk from selecting a room number.  This issue has now been resolved. The Do Not Move flag will be automatically cleared when a reservation is cancelled. Additionally, this action will be recorded in the Activity Log going forward.