Mango 3.6 Release.

Hello fellow Mango users,

We are excited to announce that Mango 3.6 is now available.  Mango 3.6 bring powerful new features that bring you more productivity, security and performance.

New :

  • New Data Source & Data Point management with bulk editing

  • New Event Detector & Event Handler management

  • New Event Handlers for Reports & Slack

  • New BACnet Device Browser and Point manager

  • New Modbus Read & Write Tools

  • Security improvements

  • Many new Admin tools now available completely in the new UI

    • BACnet Local Devices

    • System Settings

    • MangoES Configuration

    • SQL Console

  • New UI visualization components and improvements to the Dashboard Designer

Mango UI highlights

Data source and data point editor

You can now edit data sources using the new UI. Less switching to the legacy UI! Also available as a component (ma-data-source-editor) to use in your own dashboards.

Data Source Edit.png

Edit multiple data points at once.


Event handler editor

It is now easier to create event handlers set them up to handle multiple event types. Also available as a component (ma-event-handler-editor) to use in your own dashboards.


Event detector editor

Create an edit event detectors right from the Data point details page. Also available as a component (ma-event-detector-editor) to use in your own dashboards.


Better filtering of events

You can now select more specific filters from the “More options” toolbar on the events page.


Better notification of events

Mango 3.6 includes configurable notification of events via visual popups and sound.


Easily create dialogs from markup

Create your own dialogs for your dashboards using simple markup.


Detailed Release Notes

Read the detailed release notes here.

Important Notes and Highlights

  • Modify email FTL Model for events, references to evt.alarmLevel in overridden templates should be changed to evt.alarmLevel.value()

  • Default role of ‘user’ has been added.  This role is now inherent in anything that is a permissions holder.  This means that if anything has a permission of user added to it any valid User can access it. This also means that the role of user is pointless to add to any User because they inherently have it.

  • Add subject property to Email Event Handler to allow choosing what goes into the email subject. All Email event handlers are upgraded to keep legacy operation. i.e. if you previously had a name/alias set then the subject will include that

  • H2 Database upgrade to use the more performant MV Store, this also resolves the ever growing database problem.  Ensure you make a backup of your database prior to doing an upgrade.


  • Isolate v1 and v2 contexts to allow for better version management of the API, note that this isolation has resulted in some data models slightly changing.  If you are using custom code to access the API please test your code against the latest beta release

  • Data Source v2 models

  • Publisher v2 models

  • Bugfix for NPE in deprecated EmailEventHandlerModel in REST v1, suggest using v2 endpoints instead

  • Expose char(1) columns in database as boolean for RQL queries, i.e. /rest/v1/users?disabled=false or /rest/v1/users?disabled=N

  • Fix bug in RQL queries over in-memory lists where not having a sign on the sort parameter would cause the query to fail

  • Fix bug in RQL queries where empty IN clause would fail on MySQL

Serial Port

  • adding env properties serial.port.linux.readPeriods and serial.port.linux.readPeriodType to allow adjusting the rate at which the port is polled for incoming data in Linux

  • adding env property serial.port.eventQueueSize to limit the size of the queue to hold generated serial port events before they are processed

  • Purge RX/TX buffers on serial port immediately after opening it

Mango Javascript

  • Improved performance

  • Improve security when executing and testing scripts

  • Restrict Java class access for scripts without ‘superadmin’ permission

  • Improve performance when adding/removing context points to a running script

  • Add publisher control to RuntimeManager script utility

New UI Components:

  • Create and Edit Data Sources and Data Points

  • Create and Edit Event Detectors and Event Handlers

  • Report Event Handler

  • Excel Report Event Handler

  • Slack Event Handler


  • Default role of ‘user’ has been added.  This role is now inherent in anything that is a permissions holder.  This means that if anything has a permission of user added to it any valid User can access it. This also means that the role of user is pointless to add to any User because they inherently have it.

  • Users can no longer update their password to the previous password

  • DEBUG level log message for IPs that connect to a Virtual Serial Socket

  • Adding an HTTP session timeout override setting to the User

  • Show last password change date when editing a user

  • Show last login date when editing a user


  • Removing log messages from startup/shutdown status api

  • Improve performance for publishing data point attributes i.e. Reliability

  • File store definitions which do not supply permissions and no permissions definitions are found default to admin only

  • Fix bug in Change and NoChange event detectors to prevent them raising events with timestamps in the future

  • Fix bug where Change and NoChange event detectors could be initialized to wait too long for the first change/no change event

  • Optionally track anonymous usage statistics to better target future development

  • Added new Rate of Change event detector

New Modules

  • Slack Event Handler - to push events to slack channels

  • New Spanish Translation module

Mango 3.0 Upgrade Notes

Upgrading to Mango 3.0 is supported but the following items should be considered before you proceed:

  • Before upgrading to Mango 3.0 we recommend you first take a few steps:
  • Mango 3.0 requires Java JDK 8, be sure you upgrade your Java JDK before upgrading.
  • The upgrade from Mango version 2 to Mango version 3 is not free, before you upgrade we recommend you contact us to purchase a discounted upgrade license. For a limited time we will also be offering free upgrades in exchange for a short case study on your Mango application.
    • There are several new license options for Mango 3.0.  They all include the NoSQL database for no extra charge but some of them have a restricted number of data points.
  • Do a test upgrade on a copy of your Mango installation and database offline so you can understand how the process goes.
  • DGLux is not supported in Mango 3.0, if you are using DGLux we recommend that you plan to migrate your dashboards into our new HTML5 Dashboard Framework.  You can contact us to discuss this process.
  • Dashboards Module
    • If you are using the dashboards module in Mango 2.X this now deprecated and is replaced by the new MangoUI module in 3.0
      • The dashboards module is functionally identical to v3.3.1 and exists only to facilitate migration to the UI module
    • You will need to migrate your custom pages and menus from the dashboards module to the new UI module
      • There is a simple utility which will copy your old custom pages to the new UI module, navigate to /dashboards/page-migration, press “Copy” then “Save”
      • Your custom menu items will need to be manually re-created in the new UI module
      • You can uninstall the dashboards module when you are finished migrating your pages and menus
    • The AngularJS module documentation and code templates are not up to date, please hold tight for an upcoming release
  • There are many new properties in the file.  You may want to copy the new file into your overrides/properties folder and make any necessary changes.
  • NoSQL Database: All new commercial versions now include the option to use the NoSQL Database. There is a migration tool that allows you to migrate your historical data from the H2 or MySQL database into the NoSQL database.  This will give you great increases in speed and performance.
  • If after the upgrade the Mango login page fails to load in your web browser please check that you have your ad-blocker disabled for your domain. The default blocking list for several popular ad-blockers blacklists some of our JavaScript files, we will resolve this in an upcoming release.