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

  3. Anypoint Studio 7.1 with Mule Runtime Engine 4.1.2 Update Site 3 Release Notes

Anypoint Studio 7.1 with Mule Runtime Engine 4.1.2 Update Site 3 Release Notes

May 21, 2018
Build ID: 201805211625

Skip to Migration Guide

Compatibility

Product

Version

Mule Runtime

Version: 4.1.2

Anypoint Studio

Version: 7.1.3
Build Id: 201803281412

Maven

Version: 3.3.9

DataWeave

Version: 2.1.0

MUnit

Version: 2.1.4 (munit-studio-plugin)

Eclipse

Version: 4.7.2

What’s New

This version of Anypoint Studio introduces the following features:

  • Ability to send Crash Reports from Studio to help us improve our product

  • Support for Authenticated Proxies

  • Multiple Runtimes Support

This release also focuses on general bug fixes.

Hardware Requirements

  • For most use cases, Anypoint Studio with the 4.1.1 Runtime does not change hardware or software requirements from the previous Studio 7 versions.

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

  • 4GB of free memory available.

  • 2GHz CPU.

  • 10GB free hard drive space.

Software Requirements

Software

Version

Java Environments

  • Oracle JDK 1.8.0

Operating Systems

  • MacOS 10.12.0

  • Windows (32- and 64-bit) Windows 7, Windows 8, Windows 10

  • RHEL 7.0

  • Ubuntu 15.04 or later

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

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.

Migration Guide

For first time installment, refer to Studio 7.1 release notes for instructions and known issues.

Studio 7.1 only supports Mule 4.x projects. The structure of the project, export format, XML and scripting language are different.
Users must migrate Mule 3 projects to Mule 4 manually, before they can be used in Studio 7. See the Mule migration guide for more information.

Workspaces created using Anypoint Studio 6.x or below are not compatible with Anypoint Studio 7 workspaces.

From version 7.1.1 there is no special migration needed. When opening a previous Workspace which has projects that were created with Studio 7.1.0, and metadata stored in disk, Studio asks you to perform an update to all the projects so that the Metadata Manager can handle the types and to show the types in your project.

JIRA Ticket List for Anypoint Studio

Known Issues

  • Some existing features in Studio 6.x are not yet supported in Studio 7.1: Custom Policies, API Sync, Anypoint Private Cloud.

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

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

  • When referencing a RAML spec using Json Schema draft 3, DataSense fails. STUDIO-10033

  • Copybook import fails with no message. STUDIO-10206

  • Copybook import file not copied to project. STUDIO-10207

  • Menu items get grayed out after opening Exchange using XulRunner. STUDIO-9684

  • Mule modules needs to provide icons, today many of the modules have the generic icon. STUDIO-9628

  • Running application "Pom.xml" is not updated when changing dependencies. STUDIO-9148

  • Debugger: payload shown while debugging is partial but there is no way to view the rest of the payload STUDIO-9704

  • When referencing a RAML spec using Json Schema draft 3, DataSense fails STUDIO-10033

  • When setting WSC, it does not trigger datasense and not update metadata tree automatically. STUDIO-10242

  • Mule plugins with snapshot versions should always be regenerated.STUDIO-8716

  • Studio hangs when trying to open a big sample data file in DataWeave STUDIO-10523

  • When setting WSC, it does not trigger datasense and not update metadata tree automatically STUDIO-10523

  • Datasense/Runtime not working correctly through proxy on connectors using TCP/IP or connectors which don’t yet support it STUDIO-10377

  • When importing a project with a runtime that is not installed in Studio there is no notification to the User STUDIO-10892

  • Required libraries status is not refreshed in dialog after adding them STUDIO-10848

  • When changing version of a module, Studio removes it from project STUDIO-10889

  • Using the "Validate" option in your Mule configuration files is not supported.
    In your Package Explorer view, when right-clicking your Mule configuration file and selecting Validate, Studio runs a non-supported validation inherited from Eclipse. It is not recommended to use this feature.
    You can choose to disable these validators:

    • At Workspace level: By clicking Preferences, Validation, and disabling "Manual" and "Build" checkbox for XML Schema Validator and XML Validator.

    • At Project level: By right-clicking on your project in your Package Explorer View, select Properties, Validation, and disabling "Manual" and "Build" checkbox for XML Schema Validator and XML Validator.

Bug Fixes

  • STUDIO-9993 - Error types are unsorted.

  • STUDIO-10061 - When overriding maven properties used in finalName from the Run Configuration, deployment fails.

  • STUDIO-10065 - Problem with outline view icons layout.

  • STUDIO-10242 - When setting WSC, it does not trigger DataSense and not update metadata tree automatically.

  • STUDIO-10273 - When deploying to CH from Studio 7, runtimes 3.x are shown as options.

  • STUDIO-10339 - HTTP URL preview does not consider base path.

  • STUDIO-10413 - Research: Studio dies when mapping constructed with HL7 connector.

  • STUDIO-10469 - If make error in defining header response in UI, have to go to XML to fix it.

  • STUDIO-10565 - Cannot connect to Anypoint Platform from Studio 7.1.0 EA on Ubuntu 16.04 LTS.

  • STUDIO-10568 - Errors suggested within a mapping include non operation ones.

  • STUDIO-10612 - Changing metadata key options does not fetch new metadata.

  • STUDIO-10682 - Tooltips should show complete text or have option to click to see full text.

  • STUDIO-10704 - Studio searches for .properties files but not .yaml.

  • STUDIO-10731 - Improve not authorized page for deploy to cloudhub.

  • STUDIO-10734 - parse-template is not showing all configurable attributes.

  • STUDIO-10743 - Optional ExternalLibs are shown to the user as required.

  • STUDIO-10759 - Publish to exchange is showing a wrong last version when the groupId is not saved.

  • STUDIO-10764 - When setting exclusive attributes, wrong validation is being done..

  • STUDIO-10765 - Dynamic evaluate component is listed as Evaluate.

  • STUDIO-10767 - When setting transaction ID field in a flow, it loses the XML configuration.

  • STUDIO-10775 - [Deploy to cloudhub] When trying to deploy with a runtime version that is not on cloudhub, it won’t work.

  • STUDIO-10779 - Wrong metadata used in validation of DW editor with Preview on.

  • STUDIO-10785 - Blocked thread at project creation.

  • STUDIO-10787 - Use transaction id shows double colon in UI.

  • STUDIO-10791 - [SE] Error message in Publish to Exchange is incorrect.

  • STUDIO-10794 - [SE] Studio 7 does not recognize Java module exported function in DWEL.

  • STUDIO-10797 - [SE] Studio 7 doesn’t show XML files while searching for a custom settings.xml in Windows.

  • STUDIO-10815 - When publishing to exchange and typing a wrong version an invalid hint is displayed..

  • STUDIO-10821 - 403 Forbidden Error when trying to add Oracle JDBC driver.

  • STUDIO-10827 - [SE] Intermittent Studio freezes.

  • STUDIO-10838 - [SE-7907] When drag-n-dropping components between flows or in/out of Async scope doc:name attribute is duplicated.

  • STUDIO-10840 - All operations in the search area of the palette have a domain label, even when they are not in a domain.

  • STUDIO-10842 - When using APIkit module 2.0.0 the elements are shown as unknown.

  • STUDIO-10851 - [SE] When drag-n-dropping "On New File" inbound endpoint and then drag-n-dropping it back schedule properties are populated with additional opening and closing tags.

  • STUDIO-10874 - When using components that need exported resources and mule-maven-plugin 3.1.2, the application fails.

  • STUDIO-10875 - When setting a proxy and trying to publish to exchange the group id is never retrieved..

  • STUDIO-10882 - When installing a native library on the local repository without having a pom file, a pom file is not created in the local repo resulting in multiple issues.

  • STUDIO-10886 - Error thrown in the Error Log when changing the runtime in the pom and having the Mule config opened.

  • STUDIO-10887 - Wrong runtime version label when running a project.

  • STUDIO-10893 - Error thrown when creating a global SFDC configuration.

User Stories

  • STUDIO-10705 - Multiple runtime support for Studio.

  • STUDIO-10736 - Research: Send JVM reports after a crash on next startup.

Enhancement Requests

  • STUDIO-10408 - Errors that are not Handleable should not be exposed to the users.

  • STUDIO-10833 - Studio should report more accurately what it is doing when loading extension models, instead of just showing a "Downloading" message.

  • STUDIO-10873 - Same doc:id used when copy/paste an event processor.

Epics

  • STUDIO-10801 - Support for Authenticated Proxy.

Tasks

  • STUDIO-10769 - Send JVM report when studio crashes.

  • STUDIO-10770 - Create JVM crash report preference.

  • STUDIO-10771 - Add Warning dialog reporting a crash event (Phase 1).

  • STUDIO-10772 - Detect if studio opens after a crash event.

  • STUDIO-10773 - Add to jvm crash dialog with user feedback (Phase 2).

  • STUDIO-10786 - Add metrics to track when users import / export Studio projects.

  • STUDIO-10831 - Implement support for Authenticated proxies.

  • STUDIO-10866 - Upgrade default mule-maven-plugin version to 3.1.2.

  • STUDIO-10896 - Add default module versions, when server does not provide them.

Support