Last Updated: May 07, 2020
Product: Resource Management Suite Enterprise
FG #: 3004
Current Version: 4.7.0
Release Date: March 2020
-- JDK 11.0.4 and Tomcat 9.0.xx
-- RMS Enterprise will only migrate data from an RMS 3.3 database. Any older
RMS versions must first be upgraded to 3.3 before attempting to install
RMS Enterprise and migrate data to it.
-- For complete system requirements, please refer to the RMS Enterprise
Changes in this release
-- Upgraded to JDK 11.0.4 and Tomcat 9.0.xx.
-- Fixed issue- RMS fails to run when legacy mode is enabled
-- Support added for the following devices:
-- Acendo Core (ACR-5100)
-- VPX Switchers (VPX-1401/VPX-1701)
-- INCITE (813/813A/813AC)
-- Modero G5 Touch Panels(( MT-2002/ MT-1002/MD-1002/MT-702/MD-702)
-- Includes AMX License Manager v1.0.17 to support TLS v1.2.
-- Report queries that use exact whole number filter (Equal or Not Equal) in
the hour value for Lamp Hours will not return a positive report unless the
value is a whole number (does not include a decimal).
-- System upgrades from RMS 3.3 to Enterprise will initially report Hotlist
items that are based on UTC time. At the time of migration to RMS
Enterprise, the application timezone is not set, so the timestamp will
appear to be inaccurate.
-- RMS does not fully support localized floating point numbers. Due to a
limitation with Flex/Flash, the RMS user interface always displays
floating point numbers in the US format with a period (e.g. 3.14) rather
than with a comma as used in some countries (e.g. 3,14). Also, any text
fields that allow user entry of floating point numbers also require them
to be entered in the US format. The only exception is that RMS reports
do render floating point numbers correctly based upon the user's locale.
-- The mobile location scheduling view has encountered a variety of issues
on certain mobile platforms detailed below (If you experience an issue,
try Chrome, Firefox, or Safari which functioned properly in our tests):
1. The Samsung Galaxy S3 and S4 running the default browser ("Internet") on
Android 4.3 fails to render the meetings in the hourly schedule grid.
2. The Motorola Photon 4G running Android 2.3.5 crashes with a stack trace
when the mobile page display is attempted.
3. The Nokia Lumia 1020 running Internet Explorer on Windows Phone 8.0 will
only show the full meeting details if the QR code is rescanned while the
user is logged in.
4. The Nokia Lumia 2520 tablet running Internet Explorer on Windows 8.1 RT
does not display the full meeting details (only limited details can be
5. The Puffin browser on Android results in "Error 102