Anypoint Studio 7.6.0 Release Notes

July 30, 2020
Build ID: 202007250005

What’s New

Studio 7.6.0 improves collaboration in the API design process by introducing the ability to design and edit OAS 3.0 API specifications as standalone projects. This release also adds major improvements to the integration development process with key enhancements to the debugger.

  • Import and edit OAS 3.0 API specifications in Studio as standalone assets.

  • Import API specifications into standalone API projects in Studio.

  • Graphical support for the Parallel ForEach processor.

  • New default debugging perspective:

    • Improved experience setting and muting debugger breakpoints.

    • Improved debugger error messages at failing breakpoints.

    • Create conditional breakpoints with more space.

  • Package your Studio state for better joint troubleshooting.

  • Upgrade to Eclipse to 4.15.

This release upgrades the Eclipse version used by Studio.

Components Bundled With This Release

Product Version

Mule runtime engine


Apache Maven






MUnit Studio Plugin




Mule Plugin for Maven (MMP)



JDK 8 (jdk8u232-b09)

API Development Changes

Import API Specs

As with earlier versions of Studio, you can still import RAML specifications files from your local filesystem or Design Center to your projects.

You can also import RAML or OAS specifications from Exchange or a Maven repository to your projects as a dependency, and keep a pointer to that dependency to keep up to date with newer versions available. See Import an API Specification from Exchange or Maven for more information.

Edit API Specs
  • You can import a RAML, OAS 2.0, or OAS 3.0 API specification from Design Center as an editable asset in Studio and keep those changes synchronized with Design Center.
    See Synchronize API Specifications with Design Center.

  • You can also edit RAML or OAS 2.0 specifications that you imported from Exchange or Maven as your project dependencies.
    See Edit Imported API Specifications in Your Projects in Studio.

  • You can edit RAML specifications that you imported from Design Center or your local files into a Mule project however, these modifications cannot be kept in sync with your Design Center API specs.

Publish API Specs

You can publish edits you made to a RAML or OAS 2.0 API specification that you imported from Exchange or Maven into a Mule project.
See Edit Imported API Specifications in Your Projects in Studio.


Mule Runtime Engine Compatibility

Applications developed in Studio 7.5 are compatible with the following Mule runtime engine versions:

Mule Runtime Engine Version Compatible

Mule runtime engine 3.8.x


Mule runtime engine 3.9.x


Mule runtime engine 4.1.x


Mule runtime engine 4.2.x


Mule runtime engine 4.3.x

Yes (Bundled)

UI Compatibility With Application Deployment Targets

Studio 7.6 offers a graphical interface to deploy Mule 4 applications to the following application deployment targets:

Application Deployment Target Compatible



On-premises Mule runtime engine instances


Runtime Fabric

You can still deploy to Runtime Fabric by exporting your application in Studio and deploy it separately.

Compatibility With Anypoint Platform Installation Options

Studio 7.5 can integrate with the components of the following platform options:

Anypoint Platform Installation Compatible

US Cloud


EU Cloud


MuleSoft Government Cloud


Anypoint Platform Private Cloud Edition (Anypoint Platform PCE)

See configure Private Cloud Edition in Studio for more information.

Workspace Upgrade Requirements

Anypoint Studio creates workspaces in which you can create and group your projects. By default, the first time you open Studio, it creates a default workspace and holds all your projects in it. Your Mule application projects can not be fully compatible with workspaces created by a different version of Studio.

Projects created using Studio 6.x.x are not compatible with Studio 7 because they are Mule 3 projects.

See Update Workspaces for more information.

Hardware Requirements

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

  • 8GB of memory.

  • 2GHz CPU.

  • 10GB free hard drive space.

Software Requirements

  • Java Environments:
    AdoptOpenJDK 8.

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

    Studio no longer requires Java 8 to launch and run properly. Studio comes bundled with AdoptOpenJDK 8.
    You can configure Studio to start up using your preferred JDK version by following the instruction here.

    The only compatibility introduced for Java 11 is when using Mule runtime engine 4.2.0 or later.
    If you have projects running on Mule runtime engine 4.2.0 or later, and you want to run them using Java 11, see Select a Different JRE to Run the Embedded Mule Runtime Engine.

  • Operating Systems

    • macOS 10.12.0 through 10.15

    • Windows 10 (64-bit)

    • RHEL 7.0

    • Ubuntu 15.04 or later

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

  • Users must do a fresh install to upgrade from Studio 7.4.x to Studio 7.6.x.

  • As of November 2019, Studio no longer provides 32-bit binaries.

  • MUnit Studio plugin 2.1.5 does not work with this version of Studio.

  • 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.

  • Custom Policies Editor is not supported in Studio 7.x.

  • Copybook import fails with no message.

  • Copybook import file not copied to the project.

  • The pom.xml file of a running application is not updated when changing dependencies.

  • The payload shown while debugging a Mule application in the debug view is partial but there is no way to view the rest of the payload.

  • Mule plugins with snapshot versions must always be regenerated.

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

  • You won’t be notified when importing a project with a runtime that is not installed in your Studio installation.

  • Error propagation fails for API Editor.

  • Studio does not show specific error information from Design Center when publishing an API specification fails.

Fixed Issues

  • Improved overall Studio performance.

  • Improvements to the Studio debugger performance.

  • Fixed security warning message when opening Studio for the first time on Windows.

  • Fixed an issue in which adding a new Mule component to a deployed Mule application caused re-deployment errors.

  • Fixed in which a mandatory parameter wasn’t marked as such for the URI settings in a connection configuration.

  • Fixed an issue in which Anypoint Studio falsely detected file modifications while clicking inside of the Message Flow window.

  • Fixed an issue in which Studio could not find artifacts from a parent project’s dependencyManagement section.

  • Fixed an issue in which Maven settings were ignored when resolving a parent Maven dependency.

  • Fixed an issue in which scaffolding an API specification failed when the HTTP configuration was in a subcomponent.

  • Fixed error org.eclipse.swt.SWTException while using Working Sets.

  • Fixed unexpected IndexOutOfBoundException when validating a configuration file.

  • Fixed an issue in which an autogenerated application from API Manager failed to retrieve the soa-model-parent.

  • Fixed an issue in which Studio tooling was ignoring the plugincustomization field.

  • Text boxes that accept DataWeave expressions can now handle long lines of text.

  • Improved experience for specifying a domain project from a Nexus repository.

  • Fixed an issue in which Studio could not import custom modules into a Workspace from the General > Existing Projects menu.

  • Fixed an issue in which default VM arguments were not working in Anypoint Studio 7.

  • Fixed an issue in which Studio was ignoring include statements when importing an API specification.

  • Fixed an issue in which copy and pasting a Transform Message component always created a Set Payload component.

  • Fixed an issue in which Studio failed to resolve SAP dependencies.

  • Fixed an issue in which the Test Connection option in the File connector failed even when the configuration property was present.

  • Fixed an issue in which importing an Anypoint project from the file system changed the existing POM files.

  • Fixed formatting issues in the database connector editor.

  • Fixed an issue in which Studio crashed when importing an API specification from Design Center.

  • Fixed an issue in which Studio crashed when handling a big metadata type.

  • Fixed an issue in which Studio could not copy text from a Class Field editor.

  • Fixed an issue in which the Generate flow from local API menu was enabled even when no RAML file existed.

  • Fixed an issue in which creating a project with a Maven dependency did not resolve the project’s name correctly.

  • Fixed issue causing the background of the commit message window in the Git staging view was disabled after restarting Studio.

  • Fixed an issue in which the Git staging view did not refresh or allow changes on an API specification that was deleted and reimported.

  • Fixed issue preventing Linux users from deploying to CloudHub from Studio.

  • Fixed indexing issues in the API search window.

  • Fixed an issue in which Studio used the version in the Exchange model instead of the version of the asset descriptor when publishing an OAS API specification to Exchange.

  • Fixed an unhandled event loop exception when importing an API specification from Design Center.

Was this article helpful?

💙 Thanks for your feedback!

Give us your feedback!
We want to build the best documentation experience for you!
Help us improve with your feedback.
Take the survey!