Murano Release, June 15, 2017



The release notes below are intended to provide descriptions of any new features, improvements, and bug fixes included in this release of Exosite’s Murano platform. Where applicable, an explanation of the user impact is provided, as well as any additional information that may be useful.


  • Two-factor authentication is now available for Murano business account users. Two-factor authentication can be enabled in your user profile by clicking “My Profile” under the user menu. As a reminder of account security best practices, ensure your Murano user account and your email accounts are each using unique, strong passwords.


  • Watching the device logs in the Murano UI? The on-screen messaging is now clearer about the live-stream behavior of the logs page, and page rendering speed is improved when scrolling through high-volume logs.
  • The Devices page has been improved with additional content and links to help you get devices connected, so instead of staring at an empty “no devices” list, you can read up on getting started with device connectivity.
  • Adding many devices via CSV upload is now easier with the addition of an example CSV file for you to download and follow.
  • These and other UI behavior improvements allow Murano business account users to more intuitively and productively manage ADC-enabled products and applications. ADC is Murano’s Advanced Device Connectivity feature upgrade, which you can learn more about here.


  • Murano business account users will no longer receive an error message when updating the business account name.
  • Murano business account users will no longer experience Product alias conflicts when reusing an alias from a previously-deleted Product.
  • The Timer service has been corrected to ensure the UI-selected schedule frequency provides the expected results. This correction has resulted in the Timer service’s schedule() function being hidden from the Lua environment. Developers seeking to create recurring Timer events should use the sendInterval() function instead.
  • The Solution Permission Management Service (SPMS) received several updates this release, including a correction to the SPMS getRoles() function to ensure solution-specific permission data is returned for each role found and corrections that improve validation and error handling of function calls with missing or erroneous data. Many thanks to our SPMS Early Access users for your feedback and suggestions. SPMS is an Early Access service—contact us for more information.




Have more questions? Submit a request