4.7.0
Anypoint Studio 7.18.0 Release Notes
Anypoint Studio is an Eclipse-based integration development environment for designing and testing Mule applications.
June 4, 2024
What’s New
-
Studio is now packaged with Anypoint Connector for Salesforce Data Cloud (formerly Salesforce Data Cloud Connector) making it easier to connect to Data Cloud without requiring you to add the connector from Exchange.
-
Studio upgrades Mule runtime engine to 4.7 so you can work with its latest features and benefit from the fixed issues.
-
Studio now supports additional multi-factor authentication methods for your convenience.
-
AsyncAPI Beta: AsyncAPI 2.6 implementation feature is now available in Anypoint Studio 7.18.0 and later.
Before you can use these features, your Anypoint Platform organization administrator must accept the Beta terms and conditions. See Implement AsyncAPI Specifications.
To learn about the AsyncAPI journey, see AsyncAPI Support to Implement Event-Driven Architecture. Provide feedback about the AsyncAPI feature.
Compatibility
Components Bundled with This Release
Product | Version |
---|---|
Mule runtime engine |
|
DataWeave |
2.7.0 |
MUnit |
3.2.0 |
MUnit Studio Plugin |
2.7.130 |
Mule Maven Plugin |
4.2.0 |
Eclipse |
4.28 |
Maven |
3.9.6 |
Adoptium Eclipse Temurin OpenJDK |
JDK 8 (8u412-b08) JDK 17 (17.0.11_9) |
-
This version of Studio requires Java 17.
-
JDK 17 starts and runs Studio.
-
JDK 8 is the default JRE for running Mule projects and the Mule runtime instance used for tooling.
Studio 7.16 and later bundle a newer version of Apache Maven and Mule Maven Plugin. It’s not backward compatible with Apache Maven 3.8 or earlier, or Mule Maven Plugin 3.8.7 or earlier. Use your own Maven if you need an earlier version. |
Mule Runtime Engine Compatibility
Applications developed in Studio 7.18.0 are compatible with the following Mule runtime engine versions:
Mule Runtime Engine Version | Compatible |
---|---|
Mule runtime engine 3.8.x |
No* |
Mule runtime engine 3.9.x |
No** |
Mule runtime engine 4.1.x |
Yes* |
Mule runtime engine 4.2.x |
Yes* |
Mule runtime engine 4.3.x |
Yes** |
Mule runtime engine 4.4.x |
Yes |
Mule runtime engine 4.5.x |
Yes* |
Mule runtime engine 4.6.x |
Yes |
Mule runtime engine 4.7.x |
Yes*** |
* This Mule runtime version reached End of Life.
** This Mule runtime version has entered Extended Support.
*** Studio bundles this version of the Mule runtime engine.
UI Compatibility with Application Deployment Targets
Studio 7.18.0 offers a graphical interface to deploy Mule 4 applications to the following application deployment targets:
Application Deployment Target | Compatible |
---|---|
CloudHub |
Yes |
On-premises Mule runtime engine instances |
Yes |
Runtime Fabric |
No You can deploy to Runtime Fabric by exporting your application in Studio and deploying it separately. |
Compatibility with Anypoint Platform Installation Options
Studio 7.18.0 integrates with components of the following platforms:
Anypoint Platform Installation | Compatible |
---|---|
US Cloud |
Yes |
EU Cloud |
Yes |
MuleSoft Government Cloud |
Yes See Access MuleSoft Government Cloud from Studio for more information. |
Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) |
Yes Studio 7.18.0 can connect only to Anypoint Platform PCE 3.1.x and 3.2.x. See Configure Private Cloud Edition in Studio for more information. |
Workspace Upgrade Requirements
You can create and organize projects in workspaces with Studio. When you first open Studio, it automatically generates a default workspace to store your projects. Your Mule application projects might not be fully compatible with workspaces in a different version of Studio.
Projects created with Studio 6.x.x aren’t compatible with Studio 7 because they’re Mule 3 projects.
See Update Workspaces for more information.
Hardware Requirements
-
8GB of memory
Studio needs a minimum of 4GB of free RAM on a developer workstation. As applications become more complex, consider adding more RAM.
-
2GHz CPU
-
10GB free hard drive space
Software Requirements
Studio is compatible with the following operating systems and their standard configuration. Using Studio on configurations outside of the supported operating systems can result in unexpected behaviors.
-
Operating Systems
-
macOS 12 through 14
-
Windows 10, Windows 11 (64-bit)*
-
RHEL 9*
-
Ubuntu 18.04 or later LTS
-
*Windows 11 and RHEL support is based on the Eclipse support matrix. For more information, see Eclipse target environments.
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. 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 Trellix Endpoint Security Threat Prevention, Windows Security, and Broadcom Endpoint Protection. |
Fixed Issues
Issue Resolution | ID |
---|---|
Studio now resolves the |
W-15633958 |
Copy-and-pasted MUnit flows now work as expected. |
W-12289561 |
Generating a flow from WSDL no longer throws an error. |
W-14855945 |
The |
W-15571602 |
Known Issues
Known Issue | ID |
---|---|
An unknown element is created in the global-configs.xml file if implementing an AsyncAPI spec with no |
W-16195423 |
The context help wizard isn’t styled correctly in the dark theme. |
Eclipse Bug: #532184 |
Studio doesn’t support scaffolding API specs that reference OAS or JSON schema fragments imported from Exchange as project dependencies. |
W-14455756 |
Studio can ask you to trust updates on components with no digital signature when updating to the latest version of Studio. |
W-14480989 |