Last Updated: 9月30日
Product: Resource Management Suite Enterprise
FG #: 3004
Current Version: 4.8.2
Release Date: September 2021
-- JDK 11.0.4 and Tomcat 9.0.xx
-- For complete system requirements, please refer to the RMS Enterprise
Changes in this release(4.8.2)
-- Added support for wildcard (*) in reports.
-- Localization of calendar is available in all the languages.
-- In Roles Tab, if any User is associated to the Role then 'Delete' button will be disabled.
-- Many bug fixes related to Users, Roles, Reports, etc.
-- Asset Inventory Report can not be generated, if the selected Metadata is global and of type 'Date/Time',
with Minute value between 1 and 9.
-- In Reports, Location tab UI font and alignment are different than other tabs
-- In Settings tab of Location management, hover effect and font size of dropdowns are not as expected.
-- Running report by providing Decimal value in Metadata property name's Value field will throw error.
-- Intermittently Conflict error seen when try to access another page.
-- Safari is not supported at this time.
-- RFID Tracking support is not available at this time.
-- Search & Sort is restricted to the selected page in 'Configuration -> Manufacturer/Models' screen.
-- Table State(sorting/resizing/reordering) is saved for the logged-in session only.
-- Vertical Splitter for page element resizing is not implemented.
-- 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).
-- 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.
-- 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.
-- 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).