salesforce Dreamforce On-Demand
Contact Us 1-800-596-4880
  1. Homepage
  2. Archived Release Notes

  3. Anypoint Studio 7.8.0 Release Notes

Anypoint Studio 7.8.0 Release Notes

February 2, 2021
Build ID: 202101272310

What’s New

Studio 7.8.0 introduces enhancements to the API development lifecycle, including integration development for OAS 3.0 specifications and several improvements for the DataWeave editor usage experience. It also adds support for Anypoint Platform Private Cloud Edition (PCE) 3.0.

In Studio 7.8.0 and newer versions, the Java debugger is disconnected by default. See Connect the Java Debugger to connect it.

Components Bundled With This Release

Product Version

Mule runtime engine

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

Apache Maven

3.6.3

DataWeave

2.3.2

MUnit

2.3.1

MUnit Studio Plugin

2.7.1

Eclipse

4.16

Maven

3.3.9

AdoptOpenJDK

JDK 8 (jdk8u265)

API Development Changes

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

Yes

Yes

Yes

Create API implementations by importing API specifications

Yes

Yes

Yes

Import API specifications from API implementations

Yes

Yes

Yes

Edit API specifications or fragments in Studio

Yes

Yes

Yes

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

Yes

Yes

Yes

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

Yes

Yes

Yes

Scaffold a new flow from an API specification

Yes

Yes

Yes

Publish an API specification as an asset to Exchange

Yes

Yes

Yes

Compatibility

Mule Runtime Engine Compatibility

Applications developed in Studio 7.8 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 (Bundled)

UI Compatibility With Application Deployment Targets

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

Compatibility With Anypoint Platform Installation Options

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

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.8 can only connect to PCE 3.0.0.
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
      Studio 7.x suffers from degraded user interface experiences running on macOS Big Sur (11.x.x).

    • 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

  • Studio 7.x suffers from degraded user interface experiences running on macOS Big Sur (11.x.x). (SE-18760, SE-18819)

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

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

  • Metadata is not propagated on sub-flows.

  • The Apply Transformation > Function capability in the Transform Message component doesn’t work if your DataWeave script doesn’t have a header. (STUDIO-16038)

Fixed Issues

Issue Description

SE-19396

Fixed an issue that caused Studio to mark files as edited after opening them.

SE-19060

Fixed an issue that caused Studio 7.7.0 to not show a comparison of DWL files for two files and local history for a single file.

SE-18898

Fixed an issue that caused DataWeave 2.0 to have different behavior for updating functions using setVariable or setPayload compared with the Transform Message component behavior.

SE-18884

Fixed an issue that caused the XML configuration file to show as changed every time it was opened.

SE-18844

Fixed null pointer exception thrown by Studio while loading the Mule palette.

SE-18773

Fixed an issue that caused the attribute maxRetriesBefore430 to not be allowed to appear in an until-successful element.

SE-18642

Fixed an issue that caused Studio canvas to still show arrows between components inside an Error Handling scope, even after the scope was closed.

SE-18599

Fixed an issue that caused Studio to stop working when deploying to any environment.

SE-18559

Fixed an issue that prevented Studio to generate a UI for connectors if the parameter was a list of String and did not allow inline edition.

SE-18534

Fixed an issue that caused the synchronized view to stop working when DataWeave files were edited.

SE-18509

Fixed an error message thrown by Studio when a JSON file was opened.

SE-18476

Fixed an issue that caused Studio 7.7.0 to incorrectly update the dynamic parameter value ${app.runtime.default} of the <app.runtime> tag in the POM file to a static value when importing a project.

SE-18461

Fixed an issue that caused the batch:history element to throw a "no child element is expected" error when added in Studio.

SE-18302

Fixed an issue that caused Studio format XML function to not always work.

SE-18084

Studio no longer incorrectly marks an Error Handler component as a problem.

SE-18081

Fixed an issue that prevented Studio from downloading a parent POM file when loading a child project.

SE-17767

The Database InputParameters no longer shows "Missing Body Expression" event if the DataWeave header is optional.

SE-17286

Fixed an issue that prevented Studio from deploying an app if the Max in memory size value did not define a non-default value for a repeatable in-memory stream strategy.

SE-17133

Fixed an issue that prevented Studio from resolving a RAML specification when creating a Mule project using OAS2 API published in exchange.

SE-17105

Fixed an issue that prevented Studio to stop working when checking metadata for a project.

SE-16798

Fixed an issue that caused Studio to not use the metadata defined for 201 responses in POST flows.

SE-16618

Fixed an issue that caused Studio to properly escape the &#xa symbol.

SE-16240

Fixed an issue that caused Studio to change the project’s existing POM file when importing it using the * Import Anypoint project from File System* option.

SE-16146

Fixed an issue that caused Studion to create an incomplete Mule Deployable file.

SE-14271

Fixed an issue that prevented Studio from downloading artifacts in the dependencyManagement section of a parent POM file.

Support