Murano Release, May 19, 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.


  • Added the ability to publish custom Solutions as Services on the Murano Services Bus. Now Solutions that encapsulate functionality can be packaged to easily reuse that functionality in other projects.
  • Added support for the "x-host" tag to the Service swagger path in order to support Services whose functionality is hosted on multiple servers. This enables your Services to specify an "x-host" on a per-path basis to use a different server (than the default Service host) for that path.
  • The Service interface now supports named body parameters (e.g.,{"bodyParam"="String value"}). This way scripting calls to Services (that contain a body) can explicitly set parameters in the body—for example: Keystore.set({key = "x", body = {value = "value"}}).  This is helpful for Services that do not support/use json-packed inputs.


  • The Product Prototyping dashboard now supports both Murano 1.0 (legacy platform) and Advanced Device Connectivity Product types.
  • The Service schema was made more extensible by supporting the swagger tag "x-additional-events" that, when set, will allow unspecified events to be handled.


  • Fixed .init and .getRoles return codes in the early-access User and Device Grouping Service.
  • Fixed return codes when uploading content with invalid data types in the Asset Service.



Have more questions? Submit a request