ROS2006 & RVTripsetter
Release Update Page
In order to help our clients avoid unnecessary problems we have now placed our program updates in a password protected area. We want to be sure that you are downloading the proper update for your current ROS2006 or RVTripsetter version.
For Emergency Technical Support 24 Hours a day call 1-888-836-3590.
For Australian and New Zealand clients call +61 7 4925 4400
If you do not subscribe to or are not a Maintenance Plan member please have a credit card available. Charges may apply.
Select which program you need based on your business category below
--------------------------------------------------
Campground & RV Resort Users
------------------------------------------------------------
------------------------------------------------
New in Build 200
- BUG FIX: When Ros\Rvt disconnects it was crashing out of the program.
New code has been implemented so it will attempt to reconnect and if it is unable too it will inform the client there is an issue and allow them to either end the program or attempt to reconnect again.
- Code has been added so the Send_Email flag gets set correctly for declined reservations. The fix was already implemented on the server for this but this make sure the flag is set correctly anyway on the client end.
- 2 new reports added by Rob. (ConfirmG.lyo & CheckinG.lyo)
New in Build 199
This build contains:
- Bug Fix: Open_Dates for pencil-in reservations will get uploaded to the server correctly now.
- New Backup and Resort Tool: There was a bug where sequence for backups was getting lost, this has fixed the issue.
- Rez Robot bookings will always get uploaded no matter how far back they are. If the robot_uploaded flag = 0 then it will update the server with the changes.
- Cancellation email will no longer get sent if they say "No" to it.
- Ros\Rvt Rez_Number will now be uploaded to the server.
- Script will reset all "new" rez robot reservations to be uploaded so the open_dates are accurate as well as the rez_number.
- There is a new Card_Auth.dll 4.0.0.10.
- With this new DLL it will allow HOTEL clients to receive better rates on their credit card transactions when dealing with jetpay.
- I believe they will need to set this up with JetPay but when they do we need to change their preference creditauthindustryinfo.tVal from RETAIL to HOTEL.
- Contains a fix where the Ros update was not updating the database properly.
- System products will no longer be assigned to the default location with a new install.
- The "Periodic Billing" bug or Advanced Tax Issue has been fixed. (This requires significant testing please DRA).
- The Rez_Number from the front desk is now uploaded to the server so we can reference the same number the front desk is using to correlate data.
---------------------------------------------------------------
New in Build 198
-
Bug Fix: When attempting to register the program the data was getting corrupted due to the new encryption process in Build 197. This is fixed in Build 198.New Feature: When the 15 minute inactivity logout occurs, the user can now click "Cancel", which will ask if they want to terminate the program.
-
Bug Fix: Old reservations that get synced get the Open_Date set to today's date. Fixed (However all OLD reservation will not get re-uploaded unless changed)There was code saying if the open_date < today's date then use today’s date for this pencil-in. This would not have affected availability but any chance of holding old reservation information would be invalid due to this bug.
-
Bug Fix: There was a stored procedure that Receipt.lyo was calling that hung when a credit care number existed due to the new encryption process. Fixed.
What's New in Build 150 - Build 197
With Build 193, Digital Rez is providing a much harder encryption system to ensure proper storage of your customer’s credit card data, as stated in the latest requirements for Payment Card Industry (PCI) compliance. The improvements below are provided in this critical update.
New Features:
- 1. Public / Private Key Security: This update provides the resort a ‘Private Key’ which is a large string of characters that RSA encryption uses when it is encrypting and decrypting data. All credit card numbers and expiry dates are encrypted according to the accredited ‘RSA & SHA Encryption’ standard. Special Note: Loss of this Private Key file will result in the loss of any credit card data stored in the database. So, keep it stored safe, outside of the computer, preferably offsite in a secure place. Because digital files can be lost or corrupted, management may want to write the encryption password/key onto a piece of paper and have it stored safely away. Your credit card files are now stored within the systems SQL Server database records at a 1024 bit level of encryption. This exceeds current PCI requirements.
- 2. Employee Passwords: Your employees’ passwords have been encrypted and we have no back door capability to retrieve this login information via a support call. This is to ensure that the system adheres to PCI compliance standards as well.
- 3. Data Conversion : This update, once completed, applies all of the required encryption necessary to secure all of your records. Be aware that database backups made prior to this update will no longer restore properly, so ensure that all backups have been made and checked before proceeding with your update. We can only help clients recover if proper backups are available. After your update is successfully completed, be sure to make a new backup.
- 4. Credit Card Removal Tool : This update provides improvements to the Credit Card Deletion Tool. The tool is ‘Off’ by default as we cannot dictate its usage. The Credit Card Deletion Policy Setup interface provides you the ability to set the duration of retention of this information before removal.
- 5. Terminal Usage Timeout: To comply with new security requirements, the system checks for terminal activity. If within 15 minutes, the terminal remains totally inactive, the employee will be logged off and will be required to log back in to continue using the program. Login passwords must NEVER be shared.
- 6. Inactive Employee Password Renewal: If an employee has not logged into the program for 30 consecutive days, their password will be expired and must be renewed through Employee Setup by a manager.
- 7. RezRobot Version 3.0: Your RezRobot Online Booking Engine is now PCI compliant with the same security requirements that have been implemented for your front desk software. Some of the new features are outlined here.
• Secure RezExpert Oracle 11G database back end.
• PCI Compliant method of data transfer using an XML exchange.
• Public / Private Key Security.
• Credit Card Tokenization through JetPay MS.
• Non person Occupant Type handling.
• Rate quoting has been improved and exact rates are now quoted for entire length of stay selected.
• Vehicle Info improvements.
• Total Charges improved with a Tax breakdown added.
