From 5525ee0ec9e93524ce93cecb80970db41acd9bc4 Mon Sep 17 00:00:00 2001 From: Cristian-Venticinque Date: Tue, 28 Apr 2026 14:30:13 -0300 Subject: [PATCH 1/4] Updating wording with code editor. --- .../pages/_partials/acb-component-info.adoc | 34 +++++++++---------- .../_partials/acb-open-packaged-sources.adoc | 2 +- .../pages/_partials/acb-reusable-steps.adoc | 2 +- .../ROOT/pages/imp-implement-api-specs.adoc | 6 ++-- .../ROOT/pages/int-ai-gen-flow-examples.adoc | 8 ++--- .../ROOT/pages/int-autodiscovery-config.adoc | 2 +- ...nt-configure-components-open-from-xml.adoc | 2 +- .../ROOT/pages/int-configure-components.adoc | 10 +++--- .../pages/int-configure-dw-expressions.adoc | 20 +++++------ modules/ROOT/pages/int-debug-mule-apps.adoc | 12 +++---- modules/ROOT/pages/int-test-munit.adoc | 14 ++++---- modules/ROOT/pages/start-discover-ui.adoc | 2 +- .../pages/troubleshoot-missing-features.adoc | 2 +- modules/ROOT/pages/troubleshooting.adoc | 2 +- .../ROOT/pages/vibes-create-integrations.adoc | 2 +- 15 files changed, 60 insertions(+), 60 deletions(-) diff --git a/modules/ROOT/pages/_partials/acb-component-info.adoc b/modules/ROOT/pages/_partials/acb-component-info.adoc index 2a83c451c..61ea83648 100644 --- a/modules/ROOT/pages/_partials/acb-component-info.adoc +++ b/modules/ROOT/pages/_partials/acb-component-info.adoc @@ -52,8 +52,8 @@ For reference documentation on specific connector and component configurations, // // tag::note-component-add-config[] -When adding components, you can start from the canvas or the configuration XML for your app. -You can configure components from their configuration panels in the canvas or from the XML. +When adding components, you can start from the canvas or the code editor for your app. +You can configure components from their configuration panels in the canvas or from the code editor. // end::note-component-add-config[] // @@ -64,7 +64,7 @@ In Anypoint Code Builder, both integrations and implementations are Mule applica include::reuse::partial$connectors/connectors-mule-apps.adoc[] -Built-in Anypoint connectors are available from the canvas and configuration XML for integration and implementation projects. These connectors include: +Built-in Anypoint connectors are available from the canvas and code editor for integration and implementation projects. These connectors include: * xref:a2a-connector::index.adoc[Anypoint Connector for Agent2Agent (A2A) (Beta) ()] (A2A Connector) * xref:agentforce-connector::index.adoc[Anypoint Connector for Agentforce ()] (Agentforce Connector) @@ -97,7 +97,7 @@ To find information about more connectors, see xref:connectors::introduction/int Use the Connection Management Configuration Panel to easily configure connections to third-party systems directly from the UI. -In this panel, you can create, edit, delete, and test connections directly within the IDE interface, automatically populate connection fields using metadata provided by the connector, and save and manage connection configurations without switching to the XML view. +In this panel, you can create, edit, delete, and test connections directly within the IDE interface, automatically populate connection fields using metadata provided by the connector, and save and manage connection configurations without switching to the code editor. To open the configuration panel: @@ -182,7 +182,7 @@ Includes On-Error Continue (``) and On-Error Propagate (` ---- -. Add another component, this time using the configuration XML. +. Add another component, this time using the code editor. + -In the configuration XML, place your cursor before the opening `` tag. Ensure that the cursor is not inside the `` element. Add the following code: +In the code editor, place your cursor before the opening `` tag. Ensure that the cursor is not inside the `` element. Add the following code: + // image::anypoint-code-builder::add-http-config-snippet.png["http:listener-config highlighted in the configuration XML menu"] + @@ -252,7 +252,7 @@ image::anypoint-code-builder::int-canvas-error.png["Listener error in the canvas + .. To determine where the error is, select the processor in the canvas. + -Anypoint Code Builder highlights its location within the configuration XML, and you can mouse over the issue for more information, for example: +Anypoint Code Builder highlights its location in the code editor, and you can mouse over the issue for more information, for example: + image::anypoint-code-builder::int-select-listener-config.png["Selecting configuration reference from configuration panel"] .. To fix the error, change the value of the `name` attribute in `http:listener-config` to match the name of the `config-ref` value in your `http:listener` configuration: @@ -327,11 +327,11 @@ The status bar shows the progress: * *Invalid Connection Got status code: 500 when trying to resolve a Mule Runtime operation* indicates a connection error. -== Test Connection from the Configuration XML +== Test Connection from the Code Editor -You can test the connection from the configuration XML. For example, to test an HTTP Listener connection, click *Test Connection* in the configuration XML: +You can test the connection from the code editor. For example, to test an HTTP Listener connection, click *Test Connection* in the code editor: -image::http-listener-test-connection.png["HTTP Listener Test Connection link in the configuration XML"] +image::http-listener-test-connection.png["HTTP Listener Test Connection link in the code editor"] The status bar shows the progress: @@ -426,14 +426,14 @@ xref:exchange::index.adoc[]. // // tag::open-component-from-xml[] -You can open a component and its configuration panel in the canvas from the XML editor. This feature is helpful, for example, if you want to configure the component from the UI, if a component is in another flow than the flow currently displayed in the canvas, or if the canvas is not open. +You can open a component and its configuration panel in the canvas from the code editor. This feature is helpful, for example, if you want to configure the component from the UI, if a component is in another flow than the flow currently displayed in the canvas, or if the canvas is not open. -. From the configuration XML, place your cursor within the component's XML. +. From the code editor, place your cursor within the component's XML. . Right-click and select *Configure Component in UI*. + This action displays the component in the canvas and opens its configuration panel, for example: + -image::anypoint-code-builder::acb-open-component-ui-from-xml.png["Opening a component in the canvas from the XML"] +image::anypoint-code-builder::acb-open-component-ui-from-xml.png["Opening a component in the canvas from the code editor"] // end::open-component-from-xml[] // diff --git a/modules/ROOT/pages/_partials/acb-open-packaged-sources.adoc b/modules/ROOT/pages/_partials/acb-open-packaged-sources.adoc index b8790b08e..1f1289871 100644 --- a/modules/ROOT/pages/_partials/acb-open-packaged-sources.adoc +++ b/modules/ROOT/pages/_partials/acb-open-packaged-sources.adoc @@ -208,7 +208,7 @@ The root of a project is the top-level folder that Anypoint Code Builder generat // step to test the project after opening // tag::test-project[] . Test your project: -.. In the open project, check for errors and make sure that the configuration XML and canvas load correctly, which indicates that component dependencies resolved. +.. In the open project, check for errors and make sure that the canvas and code editor load correctly, which indicates that component dependencies resolved. .. Check for any configurations to modify, such as ports or file paths in the configuration XML. .. Run and debug your project: + diff --git a/modules/ROOT/pages/_partials/acb-reusable-steps.adoc b/modules/ROOT/pages/_partials/acb-reusable-steps.adoc index 8274328c6..ff6c5776c 100644 --- a/modules/ROOT/pages/_partials/acb-reusable-steps.adoc +++ b/modules/ROOT/pages/_partials/acb-reusable-steps.adoc @@ -17,7 +17,7 @@ // tag::check-connection-http[] . Before starting your Mule app, confirm that the connection to the listener is successful: + -From the configuration XML, above the HTTP Listener configuration (``), click *Test Connection*. +From the code editor, above the HTTP Listener configuration (``), click *Test Connection*. * If the test succeeds, you see a *Connection is valid* message. * If the connection fails, an error message indicates that the connection was unsuccessful. If the app is running when you click *Test Connection*, this error message appears: `Invalid Connection Got status code: 500 when trying to resolve a Mule Runtime operation. Reason: 'Internal Server Error.` diff --git a/modules/ROOT/pages/imp-implement-api-specs.adoc b/modules/ROOT/pages/imp-implement-api-specs.adoc index b700dc07a..e49b60cce 100644 --- a/modules/ROOT/pages/imp-implement-api-specs.adoc +++ b/modules/ROOT/pages/imp-implement-api-specs.adoc @@ -165,7 +165,7 @@ For example, if the updated spec adds a new endpoint, the configuration XML for == Tour the Interface File -After you scaffold your API spec into an interface, examine the scaffolded flows and error handlers for your interface in the UI canvas and configuration XML. +After you scaffold your API spec into an interface, examine the scaffolded flows and error handlers for your interface in the UI canvas and code editor. image::imp-scaffolded-flow-canvas.png["Scaffolded flows in the Canvas"] @@ -175,7 +175,7 @@ image::imp-scaffolded-flow-canvas.png["Scaffolded flows in the Canvas"] + image::int-flow-list.png["Flow List example"] -. In the configuration XML, locate the flows created for the endpoints in your API spec. +. In the code editor, locate the flows created for the endpoints in your API spec. + .Example Flow [%collapsible] @@ -261,7 +261,7 @@ and add a Flow Ref component (``) to a flow in your interface file. . Open `implementation.xml`. + image::get-flights-select-listener.png["HTTP listener highlighted in the implementation.xml file"] -. Delete the *HTTP /flights* listener XML from the configuration XML: +. In the code editor, delete the *HTTP /flights* listener XML: + [source,xml] -- diff --git a/modules/ROOT/pages/int-ai-gen-flow-examples.adoc b/modules/ROOT/pages/int-ai-gen-flow-examples.adoc index 46ade2a7b..9c6323058 100644 --- a/modules/ROOT/pages/int-ai-gen-flow-examples.adoc +++ b/modules/ROOT/pages/int-ai-gen-flow-examples.adoc @@ -71,7 +71,7 @@ After reviewing and inserting the generated flow into your project: ---- + This example flow is configured to poll for new cases every 5000 milliseconds. -. Add the required configurations for your Salesforce instance and email inbox in your configuration XML. +. Add the required configurations for your Salesforce instance and email inbox in the code editor. The following is an example of the completed flow: @@ -165,7 +165,7 @@ The `type` attribute is set to `Account` to specify the object type to update. === Complete the Flow -To run this flow, add the required configurations for your Salesforce instance in your configuration XML. +To run this flow, add the required configurations for your Salesforce instance in the code editor. The following is an example of the completed flow: @@ -265,7 +265,7 @@ output application/java After reviewing and inserting the generated flow into your project: . Update the name of the database table and fields to match what is configured in your MySQL database. -. To run this flow, add the required configurations for your Salesforce instance in your configuration XML. +. To run this flow, add the required configurations for your Salesforce instance in the code editor. The following is an example of a completed flow: @@ -372,7 +372,7 @@ After reviewing and inserting the generated flow into your project: . Update the `watermarkColumn` in the Database *Listener* to whichever database column is used to indicate new records. + The values that are taken from this column are used to filter the contents of the next poll, so that only rows with a greater watermark value are processed. -. To run this flow, add the required configurations for your database and email inbox in your configuration XML. +. To run this flow, add the required configurations for your database and email inbox in the code editor. The following is an example of the completed flow: diff --git a/modules/ROOT/pages/int-autodiscovery-config.adoc b/modules/ROOT/pages/int-autodiscovery-config.adoc index f31e3da70..643c69c3c 100644 --- a/modules/ROOT/pages/int-autodiscovery-config.adoc +++ b/modules/ROOT/pages/int-autodiscovery-config.adoc @@ -68,7 +68,7 @@ You'll need the instance ID when configuring your Mule app for autodiscovery. ==== -- . In your Mule app in Anypoint Code Builder, use your API instance ID to pair your app to the API instance: -.. In the XML editor for your Mule app, add the `` element above `` elements in the app, for example: +.. In the code editor for your Mule app, add the `` element above `` elements in the app, for example: + [source,xml] ---- diff --git a/modules/ROOT/pages/int-configure-components-open-from-xml.adoc b/modules/ROOT/pages/int-configure-components-open-from-xml.adoc index afc99cbbf..25d22163e 100644 --- a/modules/ROOT/pages/int-configure-components-open-from-xml.adoc +++ b/modules/ROOT/pages/int-configure-components-open-from-xml.adoc @@ -1,4 +1,4 @@ -= Opening a Component in the Canvas from the XML Editor += Opening a Component in the Canvas from the Code Editor :page-deployment-options: cloud-ide, desktop-ide include::reuse::partial$beta-banner.adoc[tag="anypoint-code-builder"] diff --git a/modules/ROOT/pages/int-configure-components.adoc b/modules/ROOT/pages/int-configure-components.adoc index 7f23bac66..f2a335053 100644 --- a/modules/ROOT/pages/int-configure-components.adoc +++ b/modules/ROOT/pages/int-configure-components.adoc @@ -5,7 +5,7 @@ include::reuse::partial$beta-banner.adoc[tag="anypoint-code-builder"] -Configure connectors and processors within your implementation and integration projects from the canvas or configuration XML. +Configure connectors and processors within your implementation and integration projects from the canvas or the code editor. Common tasks include the following: @@ -122,14 +122,14 @@ To copy a component: Some components, like an HTTP Listener, can't be pasted to certain locations. An error message shows if a component can't be pasted to the location. == Disable Components -You can temporarily remove components from your flow without deleting them by disabling them directly from the canvas. This action is equivalent to commenting out code in the XML editor. +You can temporarily remove components from your flow without deleting them by disabling them directly from the canvas. This action is equivalent to commenting out code in the code editor. To disable a component: . Right-click a component in the canvas. . Select *Disable Component*. -Disabled components appear with a dashed outline and a disabled icon. In the XML editor, the component is wrapped in an XML comment (), preserving the code but preventing it from executing. +Disabled components appear with a dashed outline and a disabled icon. In the code editor, the component is wrapped in an XML comment (), preserving the code but preventing it from executing. Disabled components appear greyed out in the canvas and are ignored at runtime. === Re-enable a Disabled Component @@ -138,7 +138,7 @@ To restore a component: . Right-click the disabled component. . Select *Enable Component*. -This also removes the comment from the XML view. +This also removes the comment from the code editor. If you previously set a breakpoint on a component and then disable it, the breakpoint remains associated with the component but is inactive. + You can't add new breakpoints to a disabled component until it's re-enabled. @@ -173,7 +173,7 @@ include::partial$acb-component-info.adoc[tags="import-connector-exchange"] include::partial$acb-component-info.adoc[tags="check-connection"] [[open-component-from-xml]] -== Open a Component in the Canvas from the XML Editor +== Open a Component in the Canvas from the Code Editor //open from xml include::partial$acb-component-info.adoc[tags="open-component-from-xml"] diff --git a/modules/ROOT/pages/int-configure-dw-expressions.adoc b/modules/ROOT/pages/int-configure-dw-expressions.adoc index 07f141b95..8432bca61 100644 --- a/modules/ROOT/pages/int-configure-dw-expressions.adoc +++ b/modules/ROOT/pages/int-configure-dw-expressions.adoc @@ -5,7 +5,7 @@ DataWeave is the MuleSoft programming language for data transformation and for defining expressions. -Use DataWeave to process Mule event data, such as `payload`, `attributes`, and `vars`, in connector operations and other components. Develop DataWeave expressions and transformations in your Mule applications using the *Expression Field*, *Expression Builder*, or *Transformation Builder*, or by editing the configuration XML. Generate DataWeave transformations with AI help by providing input and output sample data, metadata, or both. AI-powered auto mapping provides comprehensive error feedback for GenAI actions, including authorization, metadata, and request limits, ensuring a more reliable and guided mapping experience. +Use DataWeave to process Mule event data, such as `payload`, `attributes`, and `vars`, in connector operations and other components. Develop DataWeave expressions and transformations in your Mule applications using the *Expression Field*, *Expression Builder*, or *Transformation Builder*, or in the code editor. Generate DataWeave transformations with AI help by providing input and output sample data, metadata, or both. AI-powered auto mapping provides comprehensive error feedback for GenAI actions, including authorization, metadata, and request limits, ensuring a more reliable and guided mapping experience. image::int-dw-transform-ui.png["A configuration panel showing three numbered callouts: 1) fx button for Expression Field, 2) Expression Builder button, and 3) Transformation Builder button"] @@ -134,7 +134,7 @@ To clear custom metadata, click the name of the custom metadata and then click * [[tab-functions]] === List DataWeave Functions and Get Documentation -To get a list of available functions from a component *Functions* tab, the *fx* field, or the auto complete menu in the XML editor: +To get a list of available functions from a component *Functions* tab, the *fx* field, or the auto complete menu in the code editor: . Open a component that has the *fx* expression field. + @@ -167,7 +167,7 @@ image:int-dw-fx-functions-tab-details.png["Function details popup showing comple [[tab-preview]] === Preview Output of DataWeave Expressions -Preview output of DataWeave expressions from the canvas or from the XML editor. The preview feature acts on sample data that you provide from the configuration XML for the payload (`payload`) or Mule variables (for example, `vars.somevar`) in your *fx* (expression) field. +Preview output of DataWeave expressions from the canvas or from the code editor. The preview feature acts on sample data that you provide from the configuration XML for the payload (`payload`) or Mule variables (for example, `vars.somevar`) in your *fx* (expression) field. To provide your own sample data, see <>. @@ -197,11 +197,11 @@ image:int-dw-fx-preview-tab-output.png["Expression Builder Preview tab displayin You can apply DataWeave selectors and functions to your sample data. To create sample data that has the structure and data types you expect, see <>. [[preview-results-xml]] -==== Preview Results from the XML Editor +==== Preview Results from the Code Editor -To preview the results from the configuration XML, hover over your DataWeave code, click the *Show Code Actions* icon, and click *Run Preview*: +To preview the results from the code editor, hover over your DataWeave code, click the *Show Code Actions* icon, and click *Run Preview*: -image::function-validation-run-preview.png["Code Actions menu in XML editor with 'Run Preview' option highlighted for executing DataWeave expressions"] +image::function-validation-run-preview.png["Code Actions menu in the code editor with 'Run Preview' option highlighted for executing DataWeave expressions"] Anypoint Code Builder opens a new *Preview Output* tab with the result of the function: @@ -448,13 +448,13 @@ You can create sample data in these formats: To create sample data for a Mule variable: . Open your project. -. In the XML editor, hover over the Mule event variable (such as `payload`), for example: +. In the code editor, hover over the Mule event variable (such as `payload`), for example: + -image::int-dw-sample-quick-fix-hover.png["XML editor with cursor hovering over payload variable, showing Quick Fix for creating sample data"] +image::int-dw-sample-quick-fix-hover.png["Code editor with cursor hovering over payload variable, showing Quick Fix for creating sample data"] . Click *Quick Fix* to open the *Quick Fix* menu. . Select *Create sample data for _your-value_*, such as *Create sample data for payload*, for example: + -image::int-dw-sample-quick-fix-create.png["Quick Fix menu displaying 'Create sample data for payload' option in the XML editor context menu"] +image::int-dw-sample-quick-fix-create.png["Quick Fix menu displaying 'Create sample data for payload' option in the code editor context menu"] . In the menu that opens, select a format, such as JSON, for the sample data. + image::dw-issue-sample-data-formats.png["Sample data format selection menu showing options including JSON, XML, CSV, Java, Text, YAML, Avro, Excel, and other supported formats"] @@ -470,7 +470,7 @@ Custom sample data files should be created under `src/main/resources/user-sample + See <> before adding sample data. + -Hover over the value in the XML editor to show the structure, data keys, and data types of your sample data, for example: +Hover over the value in the code editor to show the structure, data keys, and data types of your sample data, for example: + image::int-dw-sample-quick-fix-example-hover-xml.png["Hover over XML to display sample data"] . Preview your sample data in *Expression Builder*: diff --git a/modules/ROOT/pages/int-debug-mule-apps.adoc b/modules/ROOT/pages/int-debug-mule-apps.adoc index 0ca30ffb0..6e8ff72c8 100644 --- a/modules/ROOT/pages/int-debug-mule-apps.adoc +++ b/modules/ROOT/pages/int-debug-mule-apps.adoc @@ -51,7 +51,7 @@ Keyboard shortcut: Cmd+Shift+d (Mac) or Ctrl+Shift+d (Windows) . *Call Stack* panel: Identifies the functions or procedures that are currently in the stack. . *Breakpoints* panel: Lists breakpoints by file and line, and includes <> to stop when any exception is thrown. . *Terminal* console: Displays the output of the Maven build process and the results of the deployment to the embedded Mule Runtime engine. -. *Breakpoint* icon: Identifies a line in the configuration XML to pause execution of the flow so that you can check for and fix any issues. +. *Breakpoint* icon: Identifies a line in the code editor to pause execution of the flow so that you can check for and fix any issues. . *Breakpoint* icon: Identifies a component that contains one or more breakpoints. Open the *Debug Console* tab in the panel area to <> while execution is paused. See <>. @@ -93,7 +93,7 @@ image::debug-add-breakpoint-canvas.png["Add breakpoint to a component in the can . Select *Add Breakpoint*. + -A breakpoint icon appears on the component and in the configuration XML for that component. +A breakpoint icon appears on the component and in the code editor for that component. === Add a Breakpoint to a Batch Component @@ -103,16 +103,16 @@ Add a breakpoint to a batch component in the canvas UI or in a configuration XML // Pointer to Run and Debug include::partial$acb-reusable-steps.adoc[tags="open-run-debug"] -. In the canvas UI or XML editor, select the batch component where you want to pause execution. +. In the canvas UI or code editor, select the batch component where you want to pause execution. + You can add breakpoints to these components: * Batch Job (``) * Batch Step (``) * Batch Aggregator (``) -. Right-click the component in the canvas UI and select *Add Breakpoint*, or click the line number in the XML editor. +. Right-click the component in the canvas UI and select *Add Breakpoint*, or click the line number in the code editor. + -A breakpoint icon appears on the component and in the configuration XML for that component. +A breakpoint icon appears on the component and in the code editor for that component. . Run the application in debug mode. + @@ -127,7 +127,7 @@ A conditional breakpoint uses a DataWeave expression, so execution pauses at tha To set or change a breakpoint condition: -. Add a breakpoint in the configuration XML. See <>. +. Add a breakpoint in the code editor. See <>. . Right-click the breakpoint indicator in the gutter for that line. . Select *Edit Breakpoint*. . In the breakpoint editor, enter a DataWeave expression that uses the current Mule event. diff --git a/modules/ROOT/pages/int-test-munit.adoc b/modules/ROOT/pages/int-test-munit.adoc index 397e8b4f9..2bf685753 100644 --- a/modules/ROOT/pages/int-test-munit.adoc +++ b/modules/ROOT/pages/int-test-munit.adoc @@ -51,7 +51,7 @@ A workflow can include one or more steps: [[create-tests]] == Create MUnit Tests and Test Suites -Configure MUnit tests and test suites directly from a flow or by using the canvas or XML editor. +Configure MUnit tests and test suites directly from a flow or by using the canvas or code editor. * <> * <> @@ -102,7 +102,7 @@ Anypoint Code Builder requires MUnit 3.4.0 or later to create MUnit test suites [[create-test]] === Create an MUnit Test -Create an MUnit test in a new or existing test suite. Start an MUnit test by right-clicking the `flow` component, or by using the canvas or XML editor. For guidance with your test configuration, refer to the <> described in the prerequisites. +Create an MUnit test in a new or existing test suite. Start an MUnit test by right-clicking the `flow` component, or by using the canvas or code editor. For guidance with your test configuration, refer to the <> described in the prerequisites. [[create-test-from-flow]] ==== Create a Test from a Flow @@ -120,14 +120,14 @@ Generate the basic structure for an MUnit test designed to test a specific flow See <>. [[create-test-from-xml]] -==== Create a Test from the XML Editor +==== Create a Test from the Code Editor -. Open the test suite XML in the editor. +. Open the test suite XML in the code editor. + For guidance, see <>. -. In the XML, press Ctrl+Space to display available options, and type `munit`. For example: +. In the code editor, press Ctrl+Space to display available options, and type `munit`. For example: + -image:anypoint-code-builder::munit-tests-test-xml-autocomplete.png["Using autocomplete in the XML to select the MUnit test element"] +image:anypoint-code-builder::munit-tests-test-xml-autocomplete.png["Using autocomplete in the code editor to select the MUnit test element"] . Select `munit:test` and insert the test element in your suite. For example: + [source,xml] @@ -606,7 +606,7 @@ image:acb-munit-processor.png["Component window to add a processor"] image:acb-munit-select-component-attribute.png["Component and attribute highlighted in the processor window"] . Click *Add* to add the processor to your test suite. + -The processor shows in the XML editor and the canvas. +The processor shows in the code editor and the canvas. When selecting the processor and its attributes, consider these aspects: diff --git a/modules/ROOT/pages/start-discover-ui.adoc b/modules/ROOT/pages/start-discover-ui.adoc index 577844d44..778930777 100644 --- a/modules/ROOT/pages/start-discover-ui.adoc +++ b/modules/ROOT/pages/start-discover-ui.adoc @@ -97,7 +97,7 @@ image::acb-ui-dark-theme.png["IDE using the dark theme"] == Explore the Canvas View -By default, when you open a project in Anypoint Code Builder, the canvas view opens first. This allows you to begin building and editing your flows visually, without switching to the XML editor. +By default, when you open a project in Anypoint Code Builder, the canvas view opens first. This allows you to begin building and editing your flows visually, without switching to the code editor. === Switch Views diff --git a/modules/ROOT/pages/troubleshoot-missing-features.adoc b/modules/ROOT/pages/troubleshoot-missing-features.adoc index 4f9c32e48..2918cc9d8 100644 --- a/modules/ROOT/pages/troubleshoot-missing-features.adoc +++ b/modules/ROOT/pages/troubleshoot-missing-features.adoc @@ -65,7 +65,7 @@ Workspace: Configure Workspace Trust Settings == Incomplete Flow or Corrupted XML -If a flow lacks a component or contains only a trigger, such as an HTTP Listener operation or the Scheduler, an error similar to the following appears in the *Problems* panel and from the configuration XML: +If a flow lacks a component or contains only a trigger, such as an HTTP Listener operation or the Scheduler, an error similar to the following appears in the *Problems* panel and from the code editor: ---- The content of element 'flow' is not complete. One of diff --git a/modules/ROOT/pages/troubleshooting.adoc b/modules/ROOT/pages/troubleshooting.adoc index f135d7e1d..6baea70d7 100644 --- a/modules/ROOT/pages/troubleshooting.adoc +++ b/modules/ROOT/pages/troubleshooting.adoc @@ -126,7 +126,7 @@ To disable a component: . Select *Disable Component*. -Disabled components are unavailable in the canvas and are ignored at runtime. In the XML editor, the block is wrapped in an XML comment. +Disabled components are unavailable in the canvas and are ignored at runtime. In the code editor, the block is wrapped in an XML comment. Once the issue is resolved, you can re-enable the component or use Delete to remove disabled items. diff --git a/modules/ROOT/pages/vibes-create-integrations.adoc b/modules/ROOT/pages/vibes-create-integrations.adoc index 3079e086b..f8fd3c594 100644 --- a/modules/ROOT/pages/vibes-create-integrations.adoc +++ b/modules/ROOT/pages/vibes-create-integrations.adoc @@ -78,7 +78,7 @@ After Mulesoft Vibes generates the initial integration, the code is written dire After Mulesoft Vibes builds the integration, complete the configuration as needed. Components that require further configuration display the error icon. -Select the component in the canvas to determine where the error is. Anypoint Code Builder highlights the location of the error within the configuration XML. +Select the component in the canvas to determine where the error is. Anypoint Code Builder highlights the location of the error in the code editor. == See Also From 7207fb1f31a47b7311700358bf7ef04cc161e10b Mon Sep 17 00:00:00 2001 From: Cristian-Venticinque Date: Tue, 28 Apr 2026 14:35:14 -0300 Subject: [PATCH 2/4] Additional replacements. --- modules/ROOT/pages/_partials/acb-component-info.adoc | 4 ++-- modules/ROOT/pages/int-configure-dw-expressions.adoc | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/modules/ROOT/pages/_partials/acb-component-info.adoc b/modules/ROOT/pages/_partials/acb-component-info.adoc index 61ea83648..4a873ed5c 100644 --- a/modules/ROOT/pages/_partials/acb-component-info.adoc +++ b/modules/ROOT/pages/_partials/acb-component-info.adoc @@ -117,7 +117,7 @@ You can select a previously saved connection in the *Connection* field and the f + NOTE: Changes impact all components using this connection. -* Update connection details without manually editing the XML code. +* Update connection details without manually editing the XML in the code editor. * Test the connection directly within the panel to verify it's correctly configured. + @@ -238,7 +238,7 @@ The configuration XML file now includes the XML for the HTTP Listener within the + In the code editor, place your cursor before the opening `` tag. Ensure that the cursor is not inside the `` element. Add the following code: + -// image::anypoint-code-builder::add-http-config-snippet.png["http:listener-config highlighted in the configuration XML menu"] +// image::anypoint-code-builder::add-http-config-snippet.png["http:listener-config highlighted in the code editor"] + [source,xml] ---- diff --git a/modules/ROOT/pages/int-configure-dw-expressions.adoc b/modules/ROOT/pages/int-configure-dw-expressions.adoc index 8432bca61..ed3cafd8a 100644 --- a/modules/ROOT/pages/int-configure-dw-expressions.adoc +++ b/modules/ROOT/pages/int-configure-dw-expressions.adoc @@ -65,7 +65,7 @@ For more resources, see xref:dataweave::index.adoc[]. [[open-fx-field]] == Open the Expression Field -Most connector operations and components provide at least one field that accepts DataWeave expressions and scripts. In the configuration panel for a component, the *fx* button indicates that the field accepts an expression. In the XML, these fields have the `#[]` markup. Expression fields accept DataWeave expressions, including DataWeave functions and Mule event data, such as `payload`, `attributes`, and `vars`. +Most connector operations and components provide at least one field that accepts DataWeave expressions and scripts. In the configuration panel for a component, the *fx* button indicates that the field accepts an expression. In the code editor, these fields have the `#[]` markup. Expression fields accept DataWeave expressions, including DataWeave functions and Mule event data, such as `payload`, `attributes`, and `vars`. To open a component expression field (*fx*): @@ -75,7 +75,7 @@ To open a component expression field (*fx*): + image::int-dw-fx-field-set-variable.png["Set Variable component configuration panel with the *fx* button highlighted next to the *Value* field"] + -The markup `#[]` in the *fx* field also appears in the XML to indicate that the field is for an expression. +The markup `#[]` in the *fx* field also appears in the code editor to indicate that the field is for an expression. + ---- >. From 55690b9dddea8934baf9b6e65ac42247124430b9 Mon Sep 17 00:00:00 2001 From: Cristian-Venticinque <46459586+Cristian-Venticinque@users.noreply.github.com> Date: Wed, 29 Apr 2026 17:01:01 -0300 Subject: [PATCH 3/4] Apply suggestion from @Cristian-Venticinque --- modules/ROOT/pages/_partials/acb-component-info.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/modules/ROOT/pages/_partials/acb-component-info.adoc b/modules/ROOT/pages/_partials/acb-component-info.adoc index 28b71e922..f7009726d 100644 --- a/modules/ROOT/pages/_partials/acb-component-info.adoc +++ b/modules/ROOT/pages/_partials/acb-component-info.adoc @@ -183,7 +183,6 @@ Includes On-Error Continue (``) and On-Error Propagate (` Date: Wed, 29 Apr 2026 17:01:20 -0300 Subject: [PATCH 4/4] Apply suggestion from @Cristian-Venticinque --- modules/ROOT/pages/_partials/acb-component-info.adoc | 3 --- 1 file changed, 3 deletions(-) diff --git a/modules/ROOT/pages/_partials/acb-component-info.adoc b/modules/ROOT/pages/_partials/acb-component-info.adoc index f7009726d..ce41dc828 100644 --- a/modules/ROOT/pages/_partials/acb-component-info.adoc +++ b/modules/ROOT/pages/_partials/acb-component-info.adoc @@ -182,11 +182,8 @@ Includes On-Error Continue (``) and On-Error Propagate (`