Anypoint Code Builder Release Notes

The connection configuration panel in the canvas UI adds support for configuring connections, objects, arrays of non-primitive types, and multi-level dynamic lists. In the previous release, the configuration panel supported unions, arrays of primitive types, file selectors, and password fields.

For more information, see Adding a Component to Your Project.

Connection configurations are global configurations that more than one component in a project can use. Anypoint Code Builder improves workflow by enabling you to check for components that use the connection through the UI.

For more information, see Adding a Component to Your Project.

Anypoint Code Builder adds code coverage reports for testing integration and implementation projects with MUnit.

For more information, see Running MUnit Tests with Coverage.

Additionally, you can now run MUnit tests in Anypoint Code Builder without setting your credentials in Maven.

In addition to supporting deployments of your integrations to CloudHub, Anypoint Code Builder adds support for deployments to CloudHub 2.0.

For more information, see Deploying Mule Apps to CloudHub and CloudHub 2.0.

Anypoint Code Builder adds functionality for publishing project templates and project examples to Anypoint Exchange. Publishing to Exchange enables your team to reuse your applications.

For more information, see Publishing a Mule Project to Exchange.

Anypoint Code Builder now supports creating, designing, and governing AsyncAPI 2.6 specifications.

For more information, see:

Anypoint Code Builder adds support for creating and designing Apache Avro schema fragments. Ensure data consistency and interoperability in distributed systems by defining Avro schemas with structured data, including data types and fields.

For more information, see Creating and Using API Spec Fragments

Anypoint Code Builder adds support for Solace PubSub+ and Salesforce platform events connectors.

Expand your integration capabilities and streamline event-driven architectures. For more information, see Supported Message Brokers.

Implementing AsyncAPI specifications using DataSense for Avro schemas requires Mule 4.8 or later.

Anypoint Code Builder adds support for Mule version 4.8 with Java versions 11 and 17. For more information, see Mule and Java version support.

Anypoint Code Builder introduces enhanced API auto-completion. Instead of typing Ctrl+Space to activate the auto-completion menu in your API spec, you can place your cursor at the location in your API spec file where you require suggestions. If the line has some content, press Tab, press Space, or start typing after the content on the line to launch the menu. To close the auto-completion menu, press Escape.

For more information on using auto-complete, see Use Auto-Complete in the Editors.

Anypoint Code Builder supports configuring Mule apps for tracking requests with Autodiscovery.

Configure a Mule app to send request data to an API running on a Mule Gateway runtime in API Manager. The API tracks this data in charts in API Manager.

For more information, see Tracking Requests with Autodiscovery.

Anypoint Code Builder adds breakpoint indicators in the canvas UI for components that have one or more breakpoints in the configuration XML. Indicators also display when stepping through a flow while debugging.

Additionally, you can add and remove breakpoints on components in the canvas UI.

For more information, see Debugging Mule Applications.

Anypoint Code Builder now supports custom connectors that are locally bundled or published to Exchange.

For locally bundled connectors, add the dependency to your integration project by referencing the Maven dependency in your pom.xml file.

For connectors published to Exchange, add the component from the Add Component panel using the Search in Exchange toggle.

Use the DataWeave expression builder when configuring your integrations and implementations from the UI.

DataWeave is a programming language designed for transforming data. Most components in Mule application flows use DataWeave expressions to select and transform messages (payload and attributes) or Mule variables.

The DataWeave expression builder helps you configure fields of components that accept expressions (fx fields). For each expression field, the feature provides an extra panel with the following tabs:

In addition, you can use autocomplete from an expression (fx) field for a component to select DataWeave functions from the Core module and other values accepted in this field.

For details, see Configuring DataWeave Expressions.

For more information about DataWeave and the Mule event structure, see DataWeave Overview and Mule Events.

Configure more of your integrations and implementations from the canvas UI. The configuration panel for components adds:

For examples, see Configuring DataWeave Expressions.

Anypoint Code Builder now supports Mule runtime versions 4.4, 4.6, and 4.7 and compatible Java versions (Java 11 or Java 17) to run Mule apps for your implementation and integration projects (see supported Mule and Java versions). In addition, when you create an integration project from a template or example project in Anypoint Exchange, the asset search displays assets set to use Mule 4.4 or higher, instead of 4.4 only.

Select the versions to run when creating or importing Mule applications in Anypoint Code Builder and when scaffolding an API specification into an implementation project.

The following settings are new in this release:

Anypoint Code Builder - Mule Runtime Extension (salesforce.mule-dx-mule-runtime) is removed from Anypoint Extension Pack in this release. Instead of supplying a bundled runtime, the IDE provides an interface for downloading and installing runtime versions to use in your projects.

To remove the runtime extension from VS Code, open the Extensions panel, click Anypoint Code Builder - Mule Runtime Extension, and select Uninstall.

See Version Settings for Mule, Java, and Connectors for project and default version settings.

The Java module is now bundled into Anypoint Code Builder.

When you create a new Java class in a project, Anypoint Code Builder automatically adds the necessary dependencies to the project’s pom.xml and the namespace and schema locations to the configuration XML for the project.

New integration and implementation projects now add the directories src/main/java and /src/test/java for your custom Java work.

For documentation, see Configure the Java Module Using Anypoint Code Builder.

To use auto-complete from the application XML to find module configuration options and to display lists of available Java classes and methods in a selected class, install Extension Pack for Java from Microsoft to the IDE.

To avoid changing any of your preferred Maven settings in settings.xml, Anypoint Code Builder now creates a separate settings file, acb_settings.xml.

The setting Mule: Home Directory, in the Settings tab, configures the location of this file. By default, the full path to the file is {user.home}/AnypointCodeBuilder/maven/acb_settings.xml.

For details, see Maven Settings Files in Anypoint Code Builder.

Anypoint Code Builder introduces limited support for testing with MUnit.

Run, modify, and create MUnit tests for your implementation and integration projects in Anypoint Code Builder. Import projects that contain MUnit test files. Test configuration is supported through the XML editor only at this time. For more information, see Testing Projects with MUnit.

Some MUnit features supported by Anypoint Studio are not supported by Anypoint Code Builder in this release.

Anypoint Code Builder now supports API Governance for REST APIs:

See Validating API Specifications Against Governance Rulesets.

Anypoint Code Builder introduces a configuration panel in the UI for components, such as connector operations, within integration and implementation projects. This feature simplifies component configuration.

The component configuration panel provides configuration options that are also available through the configuration XML files for your projects. Some components and fields continue to require configuration through the XML in this release. Continue to use XML for complex fields, identified as read-only fields in the UI, and for global configurations, such as connection configurations.

You can open the configuration panel from the canvas or from a configuration XML file within your project. See Add a Component to Your Project and Open a Component in the Canvas from the XML Editors.

Anypoint Code Builder adds the ability to import a template or example from Anypoint Exchange into an integration project within Anypoint Code Builder. After importing, you can continue to develop your integration. For information about templates and examples in Exchange, see Asset Types.

For guidance with importing from Exchange, click the tab Start with a Project Template or Example in the procedure Create an Integration Project.

This release introduces improvements and simplifications to the design process:

Anypoint Code Builder enables you to create one or more additional configuration XML files from within your integration or implementation projects. This feature is useful for adding an implementation for an interface. The feature also enables you to split complex project code into more manageable pieces. For more information, see Create an Additional Configuration XML File.

For more information, see Known Issues and Compatibility.