W-22293627-MS2026-05-ACB-1-19-0-CP

modules/ROOT/nav.adoc

@@ -17,20 +17,6 @@
 // TUTORIALS
 * xref:tutorials.adoc[]
 
-** xref:tut-af-amflights-overview.adoc[]
-*** xref:tut-af-design-am-flights-api.adoc[]
-**** xref:tut-af-design-api-add-request-response-details.adoc[]
-**** xref:tut-af-design-api-test-specification.adoc[]
-**** xref:tut-af-design-api-publish-api-spec-to-exchange.adoc[]
-
-*** xref:tut-af-integrate-am-flights.adoc[]
-**** xref:tut-af-integrate-connect-to-a-db.adoc[]
-**** xref:tut-af-integrate-use-dataweave.adoc[]
-
-*** xref:tut-af-implement-am-flights-api.adoc[]
-*** xref:tut-af-debug-am-flights.adoc[]
-*** xref:tut-af-deploy-am-flights.adoc[]
-
 ** xref:tut-local-api-specification.adoc[]
 
 ** xref:tut-graphql-implement-api.adoc[]
@@ -85,8 +71,8 @@
 ** xref:int-configure-components.adoc[]
 *** xref:int-configure-components-add.adoc[]
 *** xref:int-configure-dw-expressions.adoc[]
-*** xref:int-configure-components-check-connection.adoc[]
 *** xref:int-configure-components-import-connector-exchange.adoc[]
+*** xref:int-configure-components-check-connection.adoc[]
 *** xref:int-configure-components-open-from-xml.adoc[]
 ** xref:int-create-secure-configs.adoc[]
 ** xref:int-trigger-flows.adoc[]

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:/>)] (A2A Connector)
 * xref:agentforce-connector::index.adoc[Anypoint Connector for Agentforce (<ms-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: 
 
@@ -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.
 +
@@ -182,17 +182,17 @@ Includes On-Error Continue (`<on-error-continue/>`) and On-Error Propagate (`<on
 //
 // tag::add-components[]
 
-The following example illustrates basic configurations for adding components to your project from the canvas, and the configuration XML. The example assumes you are beginning with an empty integration project.
+These examples illustrate basic configurations for adding components to your project from the canvas, and the code editor. The examples assume you are beginning with an empty integration project.
 
 . {open-config-xml}, such as `my-project-name.xml`. 
 +
 image::anypoint-code-builder::int-empty-canvas.png["Canvas showing visual representation of Mule flow and the Mule configuration file"]
 +
 [calloutlist]
 .. The canvas provides space for a visual representation of your Mule flows or subflows.
-.. The configuration XML editor displays the configuration file for your Mule application.
+.. The code editor displays the configuration file for your Mule application.
 . Select *Build a Flow* from the canvas to create an empty flow within a Mule integration application.
-. Change the default name of the flow from the canvas or from the configuration XML.
+. Change the default name of the flow from the canvas or from the code editor.
 +
 [tabs]
 ====
@@ -203,7 +203,7 @@ Click *Flow name1* to open the configuration panel for the Flow component, chang
 
 image::anypoint-code-builder::int-flow-name-ui.png["Change name of flow through canvas."]
 --
-From the configuration XML::
+From the code editor::
 +
 --
 Replace the default name of the flow (`name1`) with your flow name, such as `getFlights`, for example:
@@ -234,11 +234,11 @@ The configuration XML file now includes the XML for the HTTP Listener within the
 
 </flow>
 ----
-. 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 `<flow>` tag. Ensure that the cursor is not inside the `<flow/>` element. Add the following code:
+In the code editor, place your cursor before the opening `<flow>` tag. Ensure that the cursor is not inside the `<flow/>` 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]
 ----
@@ -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:
@@ -267,8 +267,9 @@ image::anypoint-code-builder::int-select-listener-config.png["Selecting configur
 The HTTP listener within your flow now references the HTTP listener configuration, a global connection configuration that resides outside of the flow. For more information about debugging, see xref:anypoint-code-builder::debugging-mule-apps.adoc[]. 
 . Add another component to your flow.
 +
+--
 For example, add a Set Payload component to your HTTP Listener operation:
-+
+
 .. In the canvas, click the image:icon-plus.png["",15,15] (*Add component*) icon.
 .. In the *Add Component* panel, search for and select *Set payload* from the *Transformer* results.
 .. In the canvas, click *Set payload* to open its configuration panel, and add a string value, DataWeave expression, Mule variable, or configuration property.
@@ -279,17 +280,18 @@ image::anypoint-code-builder::int-set-payload-config-string.png["Adding string t
 * To add a DataWeave expression or a Mule variable as a value, such as `payload`, click *fx* (located before the field), and provide the value, for example:
 +
 image::anypoint-code-builder::int-set-payload-config-fx.png["Adding expression to Set Payload"]
-+
+
 For more information about configuring DataWeave expressions, see xref:anypoint-code-builder::int-configure-dw-expressions.adoc[].
 
 * To add a configuration property as a value, type a value such as `${secure::mysensitiveprop}`. For example:
 +
 image::anypoint-code-builder::int-set-payload-config-property.png["Adding configuration property to Set Payload"]
 +
 For more information about configuration properties, see xref:anypoint-code-builder::int-create-secure-configs.adoc[].
-
+--
++
 Your configuration XML file now looks similar to the following:
-
++
 [source,xml]
 ----
 <http:listener-config name="config-ref" >
@@ -302,6 +304,100 @@ Your configuration XML file now looks similar to the following:
 
 </flow>
 ----
+
+. Add another component to your flow.
++
+For example, add the *Create* operation from Anypoint Connector for Salesforce to insert an Account record.
++
+Use this pattern when your flow receives data through an HTTP Listener and must create Salesforce records.
+If you completed the earlier steps that add *Set payload* with a fixed string, remove or replace that processor so you can shape the payload before *Create*.
++
+For more information about using *Create* with Account records, see xref:salesforce-connector::salesforce-connector-examples.adoc[].
++
+.. In the configuration XML, add a global Salesforce connection element above your `<flow>` element (not inside the flow).
++
+Use configuration properties for credentials instead of literals; for example:
++
+[source,xml]
+----
+<salesforce:sfdc-config name="Salesforce_Config" doc:name="Salesforce Config">
+  <salesforce:basic-connection username="${salesforce.username}" password="${salesforce.password}" securityToken="${salesforce.token}" />
+</salesforce:sfdc-config>
+----
++
+For more information about connection types and authentication fields, see xref:salesforce-connector::index.adoc[].
++
+.. In the canvas, click the image:icon-plus.png["",15,15] (*Add component*) icon after *HTTP Listener*.
+.. In the *Add Component* panel, search for *Set payload*, and add the component.
+.. Configure *Set payload* with a DataWeave expression that builds a JSON object whose fields match your HTTP API (they need not match Salesforce field names yet).
++
+For example, use *fx* to enter DataWeave with `output application/json` and sample fields such as `companyName`, `industry`, and `phoneNumber`.
++
+Alternatively, add *Transform Message* and use the same DataWeave in `<ee:set-payload/>`.
++
+For more information about *Transform Message*, see xref:anypoint-code-builder::acb-component-transform.adoc[].
++
+.. From the canvas, click the image:icon-plus.png["",15,15] (*Add component*) icon after *Set payload* (or *Transform Message*).
+.. In the *Add Component* panel, click *Connectors*, select *Salesforce*, and select *Create*.
+.. In the configuration panel for *Create*, set:
++
+--
+* *Connection config*: The global Salesforce configuration name (for example, `Salesforce_Config`).
+* *Type*: `Account`.
++
+If *Type* stays empty until you establish a working Salesforce connection, set `type="Account"` on `<salesforce:create/>` in the code editor.
+* *Records*: A DataWeave expression that resolves to the records to create.
++
+If the incoming payload uses different property names than Salesforce expects, map those properties in *Records*, as shown in the configuration XML example that follows.
+If the payload is already an array of Java objects with Salesforce field names (`output application/java`), you can use `#[payload]`.
+--
++
+For more information about connector fields for this operation, see xref:salesforce-connector::index.adoc[].
++
+[NOTE]
+Picklist fields such as *Industry* must use values that exist in your Salesforce organization.
++
+This configuration listens on `/accounts`, builds a JSON payload, maps it to Account fields inside `<salesforce:records/>`, and calls *Create*.
+Align `config-ref` on `<http:listener/>` with the `name` of your `<http:listener-config/>` (for example, `config-ref` from the earlier steps in this topic).
++
+[source,xml]
+----
+<http:listener-config name="config-ref" >
+  <http:listener-connection host="0.0.0.0" port="8081" />
+</http:listener-config>
+
+<salesforce:sfdc-config name="Salesforce_Config" doc:name="Salesforce Config">
+  <salesforce:basic-connection username="${salesforce.username}" password="${salesforce.password}" securityToken="${salesforce.token}" />
+</salesforce:sfdc-config>
+
+<flow name="createSalesforceAccountFlow" >
+  <http:listener path="/accounts" config-ref="config-ref" doc:name="Listener" doc:id="rrjiqa" />
+  <set-payload doc:name="Set Payload" value="#[%dw 2.0
+output application/json
+---
+{
+  companyName: 'Anypoint Inc.',
+  industry: 'Technology',
+  phoneNumber: '415-229-2000'
+}]" />
+  <salesforce:create doc:name="Create" type="Account" config-ref="Salesforce_Config">
+    <salesforce:records>#[%dw 2.0
+output application/java
+---
+[{
+  Name: payload.companyName,
+  Industry: payload.industry,
+  Phone: payload.phoneNumber
+}]]
+    </salesforce:records>
+  </salesforce:create>
+
+</flow>
+----
++
+If the message payload is already an array of Java objects with Salesforce field names, you can omit `<salesforce:records/>` and set *Records* to `#[payload]`, or use a self-closing `<salesforce:create/>` element with that default.
++
+You can achieve the same result by adding *Transform Message* with `output application/java` followed by `<salesforce:create type="Account" config-ref="Salesforce_Config"/>` with *Records* set to `#[payload]`.
 // end::add-components[]
 //
 
@@ -327,11 +423,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 +522,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[]
 //

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: 
 +

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 (`<http:listener-config/>`), click *Test Connection*.
+From the code editor, above the HTTP Listener configuration (`<http:listener-config/>`), 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.`

modules/ROOT/pages/_partials/af-shared.adoc

@@ -63,7 +63,7 @@ To complete these tasks, you also need:
 * xref:anypoint-code-builder::start-acb.adoc[Anypoint Code Builder desktop]
 +
 Allowlist Anypoint Code Builder URLs. For more information, see xref:anypoint-code-builder::urls-to-allow.adoc[Allow URLs for Anypoint Code Builder].
-* xref:gateway::flex-gateway-managed-ingress-egress.adoc[Flex Gateway Ingress and Egress gateways]
+* xref:gateway::flex-gateway-managed-ingress-egress.adoc[Omni Gateway Ingress and Egress gateways]
 
 === MuleSoft Vibes Requirements (Optional)
 
@@ -87,7 +87,7 @@ If you're using the Anypoint CLI to create agent network projects, ensure you me
 . Use Anypoint Runtime Manager to set up a private space in CloudHub 2.0 or deployment target in Runtime Fabric.
 +
 See xref:anypoint-code-builder::af-get-started.adoc#setup-space[Set Up the Private Space or Deployment Target for Your Environment].
-. Set up Ingress and egress Flex Gateways for the private space or deployment target.
+. Set up Ingress and egress Omni Gateways for the private space or deployment target.
 +
   * If using Anypoint Code Builder, see xref:anypoint-code-builder::af-get-started.adoc#setup-gateways[Set Up Agent Network Gateways for the Private Space or Deployment Target].
   * If using the Anypoint CLI, see the xref:anypoint-code-builder::af-build-agent-networks-in-a-ci-cd-environment.adoc#agent-network-setup-gateways[setup gateways command reference].