|
|
|
Version 1.6.0
Download the latest version here. This is a new feature release, with a very
large number of changes. Many thanks to Mango users who provided their feedback and suggestions.
All of the features below were made possible by financial contributions of Mango users. Many thanks to
these companies and individuals for making Mango better for everyone!
Changes in version 1.5.0 can be found here.
|
|
Version 1.6.0 changes
- Import/Export
-
Export your configuration to a text file. Save this file for backup and recovery, or use it to import
into other instances of Mango to make identical copies. Or, use the file to manage very large
configurations easily.
- MySQL compatibility
-
Commercial Mango can now be run using MySQL as its database. Out of the box Mango will still be
configured to use Derby, but by just changing a few settings you can have it attached to an existing
MySQL instance instead. Automatic schema creation and version upgrades are still fully supported.
- Graphical refactoring
-
Graphics in Mango can now be customized into "compound" components, where one graphic can represent
multiple points.
- Long poll
-
The polling between the browser and the Mango server has been changed from being a regular timed poll
to a "long poll". This results in greatly improved network efficiency, reduced load on the server,
and generally better system responsiveness overall. Previously separated polling (i.e. view or watch
list updating and maximum alarm levels) have been consolidated into a single long poll mechanism for
additional efficiency gains.
- Audit events
-
Mango now tracks any changes (additions, updates, deletions) of runtime-affecting objects, including
data sources, data points, point event detectors, scheduled events, compound event detectors, and
event handlers. Changes will raise a new type of event, called an audit event, which describes what
was changed, and the user that did it. Event alarm levels can be managed on the system settings page,
similar to system events.
- Event acknowledgement
-
Previous versions of Mango treated an event as active or inactive based upon whether the cause of the
event had returned to normal or not. If an event cause did not naturally return to normal on its own,
the event had to be manually acknowledged by any permitted user. The version introduces the concept
of acknowledgement per user. Events will still return to normal, but all alarms must be individually
acknowedged by all recipients. Also, acknowledgement of an alarm can be done from any place where an
alarm is listed, including watch lists, graphical views, the alarm list, and the point details page.
- Alarm silencing
-
Previous versions of Mango allowed users to mute audio alarms, at least until the next page refresh,
after which the sound would need to be muted again. This version replaces this functionality by
allowing users to permanently silence an alarm (without actually acknowledging it). Once silenced, an
audio alarm will not be heard for that event by that user, even across page views and user logins. If
the alarm goes inactive and the event type is raised again, all users will hear the audio alarm
again.
- Watch list sharing
-
Similar to the existing view sharing, watch lists can now be shared among users as well. A shared
watch list will be viewed by the sharer under the permissions of the owner. The share can be
read-only (meaning that the sharer cannot set any point values), or settable (meaning that the sharer
can set any point values that the owner is able to set). Sharers are not, however, permitted to
change watch lists.
- Aliases
-
Aliases have been added to point event detectors and event handlers. These can be used to override
the default descriptions of these objects with descriptions that are more meaningful to users.
- Mango 'home' page
-
Each user can now set any application page as their 'home' page, i.e. the first page that is seen
upon login.
- Date/Time text renderer
-
A new text renderer has been added that can format numeric values as dates. Numeric values should be
some multiple of milliseconds from Jan 1, 1970 at midnight. Useful for displaying the system time of
devices or other date information.
- Point view in script context
-
The point view object has been added to the server-side script graphical renderer to provide users
with the ability to write powerful event handlers.
- SMTP port setting
-
System setting now provide a port number for the SMTP server configuration, for cases where there are
issues with using the default port 25.
- Modbus data source enhancements
-
Points that - due to their register range - are normally settable can now be set to non-settable.
This is to reflect the fact that many manufacturers put all data - read/write or read-only - into the
holding register range. Also, a checkbox for forcing contiguous batch requests only has been added.
See the documentation for more details.
- HTTP Receiver data source response content
-
Users can have the HTTP Receiver data source servlet write an arbitrary message in its response
(after any applicable warning messages) by specifying a simple system customization value in the
database. See the HTTP Receiver documentation for more details.
- z-index fix for IE
-
Issues with point views in graphics overlaying graphical charts and such has been fixed.
- Various minor enhancements and bug fixes
- Version number
- Version changed from 1.5.0 to 1.6.0
|
|
