If you’re building a production-ready Mule 4 application, you know Global Elements are the backbone of every enterprise integration – shared HTTP Listener configs, database connections, Salesforce connector credentials, property placeholders for environment-specific values, and global error handlers that keep your exception management consistent.
But until now, managing them in ACB meant hand-coding verbose XML with no visual guidance, no property placeholder management, and no AI awareness of your project’s global context. With this release, Anypoint Code Builder brings that foundational capability into a modern, AI-native experience. Whether you prefer a visual panel, natural language prompts through MuleSoft Vibes, or a combination of both. ACB generates the correct XML automatically, places it in the right file, wires up property placeholders, and validates references across your project.
Here’s what this means for your development workflow:
- Configure your way: Create and manage connector configs, properties files, and error handlers through visual forms or natural language prompts via MuleSoft Vibes. Either way, ACB generates the correct XML for you
- Seamless continuity: Whether you’re starting a new project or opening one from Studio, your global elements are recognized and manageable from day one
- Complete, deployable output: When Vibes generates a flow that uses a connector, it now includes the corresponding global config element, wires up property placeholders for credentials, and generates the properties file. The result builds and deploys without manual XML edits
What’s new: 3 pillars of Global Elements support
- The Global Elements panel
- Global configuration properties management
- MuleSoft Vibes integration
1. The Global Elements panel
A dedicated Global Elements view lives inside Project Properties, giving you a single, organized view of every global configuration in your project.
How it works:
- Navigate to Project Properties > Global Elements on any Mule project
- Select a configuration file from the dropdown to view its elements – or see everything in global-configs.xml by default
- Elements are displayed in a searchable table showing Type, Name, and Notes
- The panel updates in real time as configurations change
Adding new configurations is conversational. Use MuleSoft Vibes to describe what you need – “Add a Salesforce connector config” or “Register a new properties file” – and the element is created with the correct structure and placed in the right file.
Editing existing elements gives you the best of all worlds. For connector configurations like HTTP Listener or Salesforce, a form-driven editor lets you update connection details visually with field validation. Prefer working directly in the source? The dashboard navigates you to the exact location of the element, so you can make precise edits in context. And for natural language updates, Vibes handles modifications conversationally.
Removing configurations is handled through Vibes as well, with built-in safety checks. ACB identifies all flows that reference an element before removal, so you always understand the impact of a change before it happens.
2. Global Configuration Properties management
As a best practice, when you create a new project in ACB, it automatically generates a global-config.xml file – a dedicated, centralized place to store your configuration properties, separate from your flow configs. If you’re migrating an existing project, ACB honors your current structure as-is. This keeps your project organized from the start. ACB then provides first-class tooling for the entire properties lifecycle.
Configuration Properties registration
- Create or select a .yaml or .properties file, and ACB registers it as a
element in your global config XML - Registered files appear in the Global Elements panel under “Configuration Properties”
Multi-environment support
- ACB recognizes the ${env}.yaml dynamic file pattern out of the box
- An Environments section shows discovered env-specific files (dev.yaml, qa.yaml, prod.yaml)
- Set a default environment that maps to
- Preview mode lets you switch the active environment to verify placeholder resolution
Secure properties
- First-class tooling for the Mule Secure Properties module
- Generate encrypted property values using the secure properties JAR – no command-line gymnastics required
- ACB warns you when properties files contain unencrypted credentials
Inline Global Properties
- Add
key-value pairs directly from the UI - All managed from a single file location (global-config.xml) – no scattering across individual app XML files
3. MuleSoft Vibes integration
Previously, Vibes could generate flow logic but had no awareness of global configurations – it would either omit them entirely, inline connection details where they don’t belong, or generate incomplete configs that failed at build time. You’d finish a Vibes session and still have to hand-write the global XML yourself. That limitation is gone. Vibes now understands global elements as a first-class concept.
Automatic generation: When Vibes generates a flow that uses a connector, the corresponding global config element is included automatically. Property placeholders are used for credentials, and a sample properties file is generated. The output is immediately deployable.
Natural language management: Ask Vibes to do any of the following, or give it a more detailed prompt.
- Short prompts:
- “Create an HTTP Listener global config on port 8081”
- “Set up multi-environment configuration for dev, QA, and prod”
- “Centralize all global configs into the global-config.xml file”
- “What global elements are defined in this project?”
- “Validate my property placeholders”
- Detailed prompt: Create a Salesforce connector config named salesforceConfig using the basic provider with username ${salesforce.username}, password ${salesforce.password}, and securityToken ${salesforce.securityToken} as placeholders
Centralization assistance: If your project has global elements scattered across multiple config files (common in Studio-migrated projects), Vibes can identify them all and move them to a single global-config.xml – preserving references and updating all flow files.
How it works
At the core of this feature is the Manage Global Configurations skill – a purpose-built agent skill that powers all global element operations in ACB. Whether you’re working through the UI panel or conversing with Vibes, the same skill handles creation, editing, deletion, listing, validation, and consolidation of global configurations.
The skill covers the full spectrum: connector configs, TLS Context, Object Store, Caching Strategy, Global Error Handler, API AutoDiscovery, Import Project Reference, properties files, global-property elements, and multi-environment setup. It integrates with the MuleSoft MCP Server, exposing these operations to Vibes agentic workflows.
Beyond Connectors: Component configurations
Global Elements support extends well beyond connector configs:
| Component | What it does |
|---|---|
| Global Error Handler | Set any error handler as the application-wide default. Reference handlers from imported projects for standardized exception management across teams |
| API AutoDiscovery | Configure your Mule application to be auto-discovered by API Manager at deployment time. Flow names are discoverable from the app – no manual text entry |
| TLS Context | Set up Trust Store and Key Store configurations once, then reference them from any connector that supports TLS |
| Import Project Reference | Import a JAR containing a shared Mule project. Use its flows, error handlers, and connection configurations. ACB handles POM dependency management |
| Caching Strategy and Object Store | Define centralized caching strategies and object stores that can be referenced across all flows in the project |
How it works
At the core of this feature is the Manage Global Configurations skilla purpose-built agent skill that powers all global element operations in ACB. Whether you’re working through the UI panel or conversing with Vibes, the same skill handles creation, editing, deletion, listing, validation, and consolidation of global configurations.
The skill covers the full spectrum: connector configs, TLS Context, Object Store, Caching Strategy, Global Error Handler, API AutoDiscovery, Import Project Reference, properties files, global-property elements, and multi-environment setup. It integrates with the MuleSoft MCP Server, exposing these operations to Vibes agentic workflows.
Get started with Global Elements support
Global Elements support is now available in Anypoint Code Builder. Open any Mule project, navigate to the Global Elements panel in Project Explorer, and start managing your configurations visually, or just ask Vibes.
If you’re migrating from Studio, your existing global elements are recognized automatically. If you’re starting fresh, ACB sets up the right structure from the first project creation.
