Anypoint Studio 7.4.0 Release Notes

November 15, 2019
Build ID: 201911131921

What’s New

Studio 7.4.0 introduces the foundation for better collaboration in API development and enhances the API development lifecycle by bridging functionality.

  • Import from Exchange: Exchange is now your central source of truth for all published asset types.
    Learn more.

  • Module management: Revamped UI for module management and preferences.

  • OAS scaffolding: Support for scaffolding and implementing OAS specifications.

  • API sync: Synchronize API specifications between Anypoint Platform and Studio.
    Learn more.

  • API Search: Navigate your projects by extending the native Eclipse search feature to your Exchange dependencies.
    Learn more.

  • Support for PCE: Integrate Studio with your Anypoint Platform Private Cloud Edition deployment.
    Learn more.

This release also introduces performance enhancements reducing startup time for Studio and comes bundled with Mule runtime engine 4.2.2.

API Development Changes

Because Studio 7.4 changes behaviors in the API development lifecycle, some common tasks are impacted in this release:

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 from Maven for more information.

Edit API Specs

You can only edit RAML specifications that you imported from Design Center or your local files. You cannot edit RAML or OAS specifications that you imported from Exchange or Maven.

Publish API Specs

You cannot publish any type of API specification from Studio to Exchange.

Components Bundled With This Release

Product Version

Mule runtime engine


Apache Maven









Studio Components Compatibility

Studio 7.4 is compatible with the following bundled component/extension versions:

Product Version

Mule runtime engine

4.1.4 and later

Apache Maven

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


2.2.1 and later


2.2.0 and later


1.3.6 and later

Mule Runtime Engine Compatibility

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


UI Compatibility With Application Deployment Targets

Studio 7.4.x 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.4 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.

Projects Compatibility

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 in a Studio 6.x.x or earlier workspace

These projects are not compatible with Studio 7 because they are Mule 3 projects.

Projects created in a 7.1.x workspace

Because Studio 7.2.0 simplified the configuration of the mule-artifact.json file, if you are importing a project created in a Studio 7.1.x workspace, see Updating Workspaces for instructions to update your project structure to a compatible format.

Projects created in a Studio 7.2.x or later workspace

Projects created in this workspace are fully compatible. You can use a project created in a Studio 7.2.x workspace without performing any extra task.

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, Java 10, or Java 11.

The only compatibility introduced for Java 11 is when using Mule runtime engine 4.2.0 or later. Studio still requires Java 8 to launch and run properly. You can install and configure Java 11 on your machine, but make sure to configure this JDK to be used by the embedded 4.2.x runtime running in Studio.
See Change the JDK from Studio for instructions on how to do this.

If you are experiencing issues booting up Studio, see the troubleshooting recommendations for Windows, Linux, or MacOS.

Operating Systems

  • MacOS 10.12.0

  • Windows (64-bit)

    • Windows 7

    • Windows 8

    • Windows 10

  • 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

  • MUnit Studio plugin 2.1.5 does not work with Studio 7.4.

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

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

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

  • 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, configure Studio to use a Mozilla/XULRunner runtime environment as the underlying renderer for the Web UI. See Troubleshooting Issues with Your Default OS Browser for more details.

  • Copybook import fails with no message.

  • Copybook import file not copied to 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 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.

Bug Fixes

  • Add MacOS crashes fixes in 7.3.5

  • Fixed issue where uncommenting a DataWeave Transform Message Component in the XML editor did not cause the error on the editor to disappear.

  • Fixed issue where operations got repeated when having multiple versions of the same connector in the workspace.

  • Invalidate Key and Invalidate Cache operations now have an associated editor.

  • Fixed issue where a batch:step with the same name as a separate batch job’s batch:step could not be created.

  • Fixed issue where performing WT 10.8 caused an "Unhandled loop exception" error after editing a configuration.

  • Fixed issue where Salesforce Config modal did not fully display all fields.

  • Fixed issue where the "undo" button did not detect the changes in the Display name.

  • Fixed SocketTimeOut exception when import API from Design Center.

  • Fixed issue where user was unable to select a message processor in the outline search after importing a project from Design Center.

  • Fixed issue where applications list were empty in the run configuration view when trying to run/debug multiple applications with an external domain.

  • Fixed inconsistency in the visibility of the errors.

  • Fixed issue where an error was thrown when searching a type on an On Error continue.

  • Fixed issue where Studio did not retry deployment with Debug option.

  • Fixed wrong validation of uniqueness between flow name and batch:job jobName.

  • Fixed issue where importing an API from Design Center created an unrequired .repository folder in src/main/api/.

  • Fixed NullPointerException thrown when adding Anypoint Platform credentials.

  • Fixed issue where adding a connector inside a choice branch, it was always added at the end of that branch.

  • Fixed issue where closing all windows without saving some of them, and then accessing to delete the project an exception "Project does not exists" was thrown at the error log.

  • Fixed missing running icon in Windows.

  • Fixed issue where APIKit Router could not find the RAML specification.

  • Fixed issue where a memory leak degraded Studio performance until freeze.

  • Fixed issue where Studio 7 did not refresh external workspace modifications to files, even when using the Refresh functionality.

  • Fixed issue where Edit and Delete buttons were not made unavailable when unavailable in Windows.

  • Fixed error where a mapping through Router configuration could not be added on Exchange applications.

  • Fixed error where an error was logged when right-clicking over the JAR files on the Package Explorer.

  • Fixed error where suggested mappings list did not show resources parameters.

  • Fixed error where the Studio Build Helper plugin set an absolute path when running on Windows.

  • Fixed difference in UI display/icon for REST Connector.

  • Fixed NullPointerException when reading a project from Exchange.

  • Fixed issue where Studio 7 did not show links to classes in Console View.

  • Fixed issue where Studio could not find com.mulesoft.mule.agent when debugging an MUnit suite.

  • Fixed issue where it was not possible to assign a variable in an API module processor when it expected an Enum value.

  • Fixed issue where cleaning up resources for Tooling was not removing cached extension models on file system for Tooling Runtime Client.

  • Fixed Maven preferences table to have only two columns.

  • Fixed issue where Maven Global configurations edit was not being disabled when the user uses an embedded Maven installation.

  • Fixed issue where user could add duplicated Maven server configurations.

  • Fixed issue where Maven server configuration did not check for user writing permissions.

  • Fixed UI error when editing a DataWeave script when using a map operator.

  • Fixed issue where followRedirect option in http:request was not set to false when box was unchecked.

  • Fixed issue where Studio did not scaffold a public API.

  • Fixed stackoverflow being thrown when using a new metadata mode.

  • Fixed issue where validation of a module dependency was too slow.

  • Fixed issue where an API specification was not being read right after importing it.

  • Fixed NullPointerException thrown when a project was deleted.

  • Fixed issue where a SWTException: Invalid thread access was thrown when adding a module to the Mule palette.

  • Fixed issue where an MUnit run was not deleted causing new nodes to throw errors.

  • Fixed issue preventing to add modules to favorites from the Mule palette search results.

  • Fixed issue where an error was thrown when Studio tried to resolve any metadata from org.mule.tooling.core plugin.

  • Fixed issue where Mule Server Manager took too long to start.

  • Fixed issue where property placeholders were detected as DataWeave expressions and triggered errors for attributes that don’t allow expressions.

  • Fixed issue where trying to drag & drop in DataWeave mapping editor did not work if script contained plain objects.

  • Fixed issue where validating MUnit resources caused a CPU dead lock.

  • Fixed issue where Studio incorrectly changed connectors error types to upper case.

  • Fixed issue where Studio could not import a JSON Schema by using the Manage Metadata Types option.

  • Fixed issue where Studio incorrectly flagged as an error a commented line at the end of a DataWeave script.

  • Fixed issue where the Web Service Consumer did not propagate metadata when namespace of attributes was missing.

  • Fixed issue where Mule runtime engine version set in MUnit Run Configurations was cleared if test is not run from Run Configurations window.

  • Fixed issue where resizing a tab in the debug mode permanently closed the console.

  • Fixed issue where importing a shared configuration file using backlash as a directory separator threw an error.

  • Fixed issue where SAP Native Library was not being detected.

  • Fixed issue where importing an API specification from Design Center using Windows broke the specification encoding.

  • Fixed issue where Scatter-Gather component was not supported when running on debug mode.

  • Fixed issue where Studio generated multiple indexing threads on project creation.

  • Fixed issue where dynamic names in DataWeave Studio grammar was not supported.

  • Fixed issue where the mule-artifact.json file was being overwritten when importing an existing project created in Studio 7.3.5.

Enhancements Request

  • Improved start-up time of Studio.

  • Reduced the amount of entries logged in the error log at startup.

  • Enabled "Publish to Exchange" and "Deploy to cloud" from context menu on all project elements.

  • Added support for stereotypes when selecting connection providers.

  • MetadataKey resolution runs in background.

  • Added support for RAML data types to define metadata in Transform Message component.

  • Added support for improved lightweight deployment model from packager and Tooling.

  • Enabled users to reference mule-plugins that have no extension model.

  • ScaffoldingResultNotifications now appears in Error Log too.

  • Added a facility for performing batchable background work.

  • Changed Exchange Dependencies label in Search In option in API search tab.

  • Enabled field editors to be refreshed on changes located in other groups.

  • Added info message to progress bar while importing an API from Design Center.

Was this article helpful?

💙 Thanks for your feedback!