Anypoint Studio 7.11 Release Notes

Anypoint Studio is an Eclipse-based integration development environment for designing and testing Mule applications.

October 5, 2021

What’s New

  • Added support for Mule runtime engine 4.4.
    Learn more in What’s New in Mule 4.4.

  • Added Secure Storage.
    Learn more in Secure Storage Overview.

  • Dataweave 2.4.
    Learn more in What’s New in DataWeave.

  • Added Referenced By option for flows and subflows.
    You can right-click on a flow or subflow and select the Referenced by option to get a list of Flow Reference components that reference your selected flow.


Components Bundled With This Release

Product Version

Mule runtime engine






MUnit Studio Plugin







JDK 8 (AdoptOpenJDK 8u282-b08)
JDK 11 (AdoptOpenJDK 11.0.10_9)

Mule Runtime Engine Compatibility

Applications developed in Studio 7.11 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


Mule runtime engine 4.4.x

Yes (Bundled)

UI Compatibility With Application Deployment Targets

Studio 7.11 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 deploy to Runtime Fabric by exporting your application in Studio and deploying it separately.

Compatibility With Anypoint Platform Installation Options

Studio 7.11 can integrate with the components of the following platforms:

Anypoint Platform Installation Compatible

US Cloud


EU Cloud


MuleSoft Government Cloud

See access MuleSoft Government Cloud from Studio for more information.

Anypoint Platform Private Cloud Edition (Anypoint Platform PCE)

Studio 7.11 can connect only to PCE 3.0.0 and 3.0.1.
See configure Private Cloud Edition in Studio for more information.

Before attempting to connect to Anypoint Platform by using multi-factor authentication (MFA), change the Browser setting from Built-in to Native.
See Configure Studio’s Browser Settings.

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 might 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

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

  • 2GHz CPU.

  • 10GB free hard drive space.

Apple M1 processors have not been thoroughly tested on Studio 7.11. Please, proceed with caution.

Software Requirements

  • Java Environments:
    Studio bundles two different JDKs:

    • AdoptOpenJDK 11 (11.0.10_9)
      JDK 11 starts and runs Studio and the Mule runtime instance used for tooling.

    • AdoptOpenJDK 8 (8u282-b08)
      JDK 8 is the default JRE for running Mule projects

      You can configure Studio to start using your preferred JDK version by following the Configure Studio to Use Your Own JDK steps.

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

  • Operating Systems

    • macOS 10.12.0 through 11.0.0

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

Fixed Issues

Issue ID

Exporting metadata to a sub-flow no longer fails with the error “The Dataweave script generated contains errors and cannot be used to generate custom metadata” when generating an invalid custom type.


Fixed An internal error occurred during: "Reload types…​" error when creating a new metadata definition using the Transform Message component in a flow.


Fixed issues when scaffolding OAS 3.0 API specifications.

SE-19653, SE-20212, SE-20368

Improved metadata resolution from an XSD schema or an XML example in a RAML specification.


Improved error messaging when re-publishing an asset to Exchange using a different project type.


Removed incorrect error message when using Web Service Consumer module because Studio could not resolve SOAP properties located within the propertiesCollection.


Known Issues

Known Issue ID

Toolbar buttons in Views disappear after some combination of state and actions.

Eclipse Bug #572598

Context help wizard is not styled correctly in dark theme.

Eclipse Bug #532184

The input/output panes of the Transform Message component display an incorrect background color when using the light theme.


Was this article helpful?

💙 Thanks for your feedback!