Anypoint Studio 7.2 with Mule Runtime Engine 4.1.3 Update Site 3 Release Notes

September 24, 2018
Build ID: 201809241236




Mule Runtime

Version: 4.1.3

Anypoint Studio

Version: 7.2.3
Build Id: 201809241236


Version: 3.3.9


Version: 2.1.4


Version: 2.1.4 (munit-studio-plugin)


Version: 4.7.2

Projects created or updated with Studio 7.2.x are not compatible with 7.1.x due to some improvements with the management of the mule-artifact.json file. The content of the file was reduced and part of the content used to be required by Studio 7.1.x.
To fix this issue you only need to update Studio to the latest 7.2.x version available. See Updating Workspaces for more information.

Workspaces created using Anypoint Studio 6.x or below are not compatible with Anypoint Studio 7 workspaces.

What’s New

This version of Anypoint Studio introduces bug fixes.

Hardware Requirements

  • For most use cases, Anypoint Studio with the 4.1.3 Runtime does not change hardware or software requirements from the previous Studio 7 versions.

  • MuleSoft recommends a minimum of 4GB of free RAM available on a developer workstation. As applications become complex, consider adding more RAM.

  • 4GB of free memory available.

  • 2GHz CPU.

  • 10GB free hard drive space.

Software Requirements



Java Environments

  • Oracle JDK 1.8.0

This version of Studio is not compatible with Java 9 or Java 10.

Operating Systems

  • MacOS 10.12.0

  • Windows (32- and 64-bit) Windows 7, Windows 8, Windows 10

  • RHEL 7.0

  • Ubuntu 15.04 or later


Studio comes with Maven 3.3.9 bundled, but you can externally use the versions: 3.3.3 or your own 3.3.9

Running real-time antivirus protection software on your operating system might have a negative impact on Anypoint Studio performance. Although this issue is prominent on Windows, it also occurs on Linux and macOS.

Although the steps to solve these performance issues vary depending on your antivirus software, a typical solution is to either allow or exclude the Anypoint Studio and java executables, the Studio install and workspace filesystem locations, or some combination of both. See examples of solutions for McAfee Viruscan, Windows Defender, and Symantec Endpoint Protection.

Known Issues

  • Studio 7.2.3 only supports Mule 4.x projects. Due to the structure of projects, export format, xml and scripting language differences, we do not offer backwards compatibility with Mule 3.x runtimes.

  • Because the metadata propagation works differently in Studio 7, Datasense might display errors if your DataWeave code has references to unknown metadata either because you didn’t define the metadata before writing your code, or because your flow is still incomplete.
    See Understanding How DataSense Uses Mule Event Metadata and Transform Message Component for more information.

  • Some existing features in Studio 6.x are not yet supported in Studio 7: Custom Policies, API Sync, Anypoint Private Cloud.

  • Anypoint Studio uses your configured default browser to display web content such as Exchange and the Runtime Manager UI when deploying an application to Anypoint Platform. If your default internet browser does not display this content correctly, you can configure Anypoint Studio to use a Mozilla/XULRunner runtime environment as the underlying renderer for the Web UI.
    Follow the FAQ: Troubleshooting Issues with Your Default OS Browser for more details.

  • Copybook import fails with no message.

  • Copybook import file not copied to project.

  • Mule modules needs to provide icons, today many of the modules have the generic icon.

  • Running application "Pom.xml" is not updated when changing dependencies.

  • Debugger: payload shown while debugging is partial but there is no way to view the rest of the payload

  • Mule plugins with snapshot versions should always be regenerated.

  • Datasense/Runtime not working correctly through proxy on connectors using TCP/IP or connectors which don’t yet support it.

  • When importing a project with a runtime that is not installed in Studio there is no notification to the User.

  • Define Metadata - selected schema file does not exist when I have an example JSON set for the metadata type.

Bug Fixes

  • Warning about jetty server not stable release.

  • Incorrect JDBC Driver is missing error when using generic db connector.

  • Debugger does not highlight the processor that it’s executing.

  • Mule Schema namespaces not generated when moving configuration elements between different Mule Configuration Files.

  • Unavailable Maven dependency for APIKit for SOAP.

  • When editing connector from Datasense error popup, the file contents is deleted.

  • [SE] AnyPoint Studio deletes contents of file on Salesforce connection error.

  • When extracting to a flow in a closed configuration file, it deletes xml code.

  • When closing a domain linked to a project, it hangs.

  • When referencing a domain in your M2, it never ends to resolve that dependency.

  • When editing global configs opened from warning popup, it deletes xml code.

  • When adding maven dependencies as provided, nothing happens.

Was this article helpful?

💙 Thanks for your feedback!