Anypoint Studio 7.7.0 Release Notes

October 29, 2020
Build ID: 202010222232

What’s New

Studio 7.7.0 introduces core infrastructure upgrades as well as enhancements to the API development lifecycle, including API and integration development, and platform development collaboration.

This version also features support for MuleSoft Government Cloud integration, and several improvements for the Dataweave editor usage experience, including smart auto-generated examples and an enhanced data-driven transformation experience.

  • Core infrastructure upgrades:

    • Upgrade to Eclipse 4.16.

    • Support for Mule 4.3.0 September 2020 patch.
      Studio embeds a version of the Mule runtime engine based on the September 2020 patch (4.3.0-20200824) with additional improvements to the API design experience.

    • NPS survey in the welcome dialog.

  • Enhancements to the API development lifecycle, and platform collaboration:

    • Create API specifications in Studio using a new API Design perspective, and synchronize it with Design Center.

    • Mock API specifications using the new API console.

  • MuleSoft Government Cloud Support.

    • Import and publish your assets to MuleSoft Government Cloud Exchange.

    • Reuse domain projects in your Mule project built in conjunction with a non-MuleSoft Government Cloud Anypoint Platform organization saved on your local file system.

    • Deploy your Mule project from Studio to MuleSoft Government Cloud.

    • Leverage the full API development lifecycle supported by Studio.
      See API Development in Studio for the full list of available tasks.

  • Improvements to the Dataweave editor:

    • Better auto-generated sample data based on your input metadata.

    • You can now see sample data and transformation results in the Data Structure view which provides a more data-driven experience.

You can upgrade to this version using the Studio update site.
If you are upgrading from Studio 7.4.x or earlier versions, you must download a fresh installation of Studio. See Download and Install Studio for instructions.

Components Bundled With This Release

Product Version

Mule runtime engine

This version is based on 4.3.0-20200824 with additional improvements to the API design experience.

Apache Maven






MUnit Studio Plugin







JDK 8 (jdk8u265)

MuleSoft Government Cloud Support

Studio now supports Single Sign-On (SSO) to configure and use any identity provider (IdP) to authenticate to Anypoint Platform. Studio can now leverage the same SSO support for MuleSoft Government Cloud setups. See Access MuleSoft Government Cloud from Studio for more information.

API Development Changes

Create API Specifications

Studio 7.7.0 and later enables you to create a RAML 1.0, OAS 2.0 or 3.0 API specification, or an API fragment in Studio and automatically synchronize it with Design Center. See Create an API Spec in Studio for more information.

See the following table for the available API development tasks supported by specification type:

Task RAML OAS 2.0 OAS 3.0

Create API specifications from scratch




Create API implementations by importing API specifications




Import API specifications from API implementations




Edit API specifications or fragments in Studio




Retrieve changes from Design Center to an API specification imported into Studio




Push changes from Studio to an API specification imported and synchronized with Design Center




Publish an API specification as an asset to Exchange





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

See access MuleSoft Government Cloud from Studio for more information.

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

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

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

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

  • Mule runtime engine crashes after consecutive redeployments in debug mode.

  • XML flow files fail to render if pom.xml file is invalid.

  • Issues on mocking service when renaming an API Project.

  • Misalignment of labels on the exchange.json editor.

  • Confusing error message when using a non-semantic version number for API version when publishing to Exchange.

  • Dataweave function button (Fx) does not switch to Expression mode on Salesforce connector.

  • Metadata is not propagated on sub-flows.

  • The Evaluate DataWeave expression view shows an error when launching the debug perspective.

  • In the API Console view, the scrollbar overlaps the header.

  • NoSuchFieldException after cleanup of JDBC resources (MySQL) while redeploying an app.

  • Unstaged changes are not shown after renaming API until focus is restored.

  • exchange.json file can’t be saved after renaming an API specification project.

  • exchange.json editor is damaged after reopening an API specification project.

  • No action for the Powered by Mulesoft link in the API Console view.

  • Munit test fails if a recorded flow makes an HTTP request to another flow.

  • Configuring a Spy processor in an MUnit test case creates a copy of the same attribute multiple times.

  • The API Console view is not updated after an OAS 3.0 specification is updated.

Fixed Issues

Issue Description


Metadata was not generated correctly when <ROW> tag is duplicated.


Updating a field in the graphical user interface results in malformed XML.


Changes made in the Properties editor do not get saved in the XML configuration.


Faulty configuration XML may be generated when an HTTP Request component is cloned using CTRL + drag.


Missing schemaLocation declarations in the XML Configuration files.


Studio stops responding when a leading space is entered in the Exchange search bar.


Studio displays errors in DataWeave scripts generated by the Mule migration assistant.


Transform Message Component showing error in DataWeave.


Go To Node option is missing in the XML source of MUnit files.


Studio stopped allowing new components to be added from the Mule palette to the message flow canvas.


Required attribute name is not defined in the flow-ref component.


Editing DataWeave causes Studio to stop responding and results in high CPU and memory utilization.

SE-17231 / SE-17541

Fixed an issue that caused Studio to fail to build a newly imported project because it was unable to resolve Spring modules.


When doing an update on a scaffolded API from Exchange and a previous API is deployed, the new version failed to be applied with a Scaffolding Error message.


Fixed an issue in which Studio was not correctly recognizing the presence of SAP connector library dependencies in transitive dependencies.


Clicking the Error Handling section of a Try scope and then clicking outside of it caused the Studio editor to treat the file as modified.


Fixed an issue in which Studio was not responding when any change was made to the DataWeave transform message component.


Fixed Studio metadata warnings with EDI X12 Connector.


Fixed an issue in which Studio was unable to download parent POM file when loading child project.


Fixed an issue that caused Studio to stop responding while reading FFD with composite referencing undefined element ID.


Fixed an issue in which sample data was not created for user-defined metadata in DataWeave for Mule 4.


Fixed an issue that caused Studio to fail to import a project when having a dependency on an artifact defined in the parent’s dependencyManagement section.

Was this article helpful?

💙 Thanks for your feedback!