# Salesforce Connector Release Notes

Support Category:
[Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf)

Anypoint Connector for Salesforce (Salesforce Connector) provides access to the Salesforce APIs.

Guide: [Salesforce Connector](../../salesforce-connector/latest/)  
Reference: [Salesforce Connector Reference](../../salesforce-connector/latest/salesforce-connector-reference)

## 11.4.0

**April 5, 2026**

### What’s New

- Salesforce Connector now supports Salesforce API v66.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The variable name for <strong>Time unit</strong> is changed from <code>objectTTLUnit</code> to <code>objectTTLTimeUnit</code>. The display name (<strong>Time unit</strong>) remains unchanged.</p></div></div></td><td><p>W-21082898</p></td></tr><tr><td><div><div><p>These libraries are upgraded to address reported security vulnerabilities:</p></div><div><ul><li><p>The <code>jackson-core</code> library is upgraded to version 2.18.6.</p></li><li><p>The <code>commons-text</code> library is upgraded to version 1.14.0.</p></li><li><p>The <code>guava</code> library is upgraded to version 32.1.3-jre.</p></li><li><p>The <code>mule-connector-logging</code> library is upgraded to version 1.0.2.</p></li></ul></div></div></td><td><p>W-21713141</p></td></tr></tbody></table>

## 11.3.4

**March 20, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The variable names for <strong>Object TTL</strong> and <strong>Time unit</strong> are changed from <code>objectTTLTimeout</code> and <code>objectTTLTimeoutUnit</code> to <code>objectTTL</code> and <code>objectTTLUnit</code> to resolve a backward compatibility break introduced in version 11.3.0. Previously, this change caused existing applications to fail during build with an error stating that the <code>objectTTL</code> attribute was not allowed. The display names (<strong>Object TTL</strong> and <strong>Time unit</strong>) remain unchanged.</p></td><td><p>W-21082898</p></td></tr><tr><td><p>The <code>jetty.version</code> library is upgraded to version 9.4.58.v20250814 to address reported security vulnerabilities.</p></td><td><p>W-21577093</p></td></tr></tbody></table>

## 11.3.3

**January 21, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Token</strong> field is renamed to <strong>Security Token</strong> for the <strong>Basic Authentication</strong> connection type.</p></td><td><p>W-19987844</p></td></tr><tr><td><p>The connector now handles Apex class failure responses correctly and no longer throws the <code>java.lang.ClassCastException</code> error when propagating errors from Salesforce. Previously, when an Apex class returned a failure response code, the connector failed to cast <code>SalesforceException</code> to <code>ModuleException</code>, preventing proper error propagation.</p></td><td><p>W-20089710</p></td></tr><tr><td><p>The connector now correctly closes the streaming connection for the <strong>Replay Channel Listener</strong> source before attempting a source restart during <code>403</code> or <code>401</code> error scenarios. By stopping the streaming client before raising a connection exception, the connector prevents a leak where multiple client IDs remain active and receive the same platform events.</p></td><td><p>W-20604291</p></td></tr></tbody></table>

## 11.3.2

**December 7, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector with the <strong>OAuth Client Credentials</strong> connection type now renews the token when an <code>INVALID_SESSION_ID</code> error occurs in the <strong>Create Job</strong> and <strong>Create Job Bulk Api V2</strong> operations.</p></td><td><p>W-19714693</p></td></tr></tbody></table>

## 11.3.1

**November 19, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The Spring Framework dependency now excludes the <code>spring-context</code> and <code>spring-aop</code> libraries to address the <code>CVE-2024-38820</code> security vulnerability.</p></td><td><p>W-19805552</p></td></tr></tbody></table>

## 11.3.0

**October 3, 2025**

### What’s New

- Salesforce Connector now supports Salesforce API v65.0.
- The connector no longer supports the **Basic Authentication** connection type for the Salesforce
  API v65.0.
- The variable names for **Object TTL** and **Time unit** are changed from `objectTTL` and
  `objectTTLTimeUnit` to `objectTTLTimeout` and `objectTTLTimeoutUnit`. The display names (**Object
  TTL** and **Time unit**) remain unchanged.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0</p></td></tr></tbody></table>

## 11.2.3

**September 12, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>For the <strong>OAuth JWT</strong> connection type, the connector now uses the <code>SHA256WithRSA</code> algorithm to sign certificates by default.</p></td><td><p>W-19075988</p></td></tr></tbody></table>

## 11.2.2

**September 4, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Query xml stream</strong> operation now correctly throws the <code>SALESFORCE:INVALID_INPUT</code> error instead of the <code>MULE:UNKNOWN</code> error when invalid input is provided.</p></td><td><p>W-18779869</p></td></tr><tr><td><p>The connector with the <strong>OAuth Client Credentials</strong> connection type now renews the token when an <code>INVALID_SESSION_ID</code> error occurs in the <strong>Invoke apex rest method</strong> operation.</p></td><td><p>W-19003555</p></td></tr></tbody></table>

## 11.2.1

**August 10, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now restarts the source when the disconnect message doesn’t contain an error message.</p></td><td><p>W-19152788</p></td></tr><tr><td><p>The <code>org.apache.commons:commons-lang3</code> library is upgraded to version 3.18.0 to address reported security vulnerabilities.</p></td><td><p>W-19292855</p></td></tr><tr><td><p>The <code>commons-lang:commons-lang:2.6</code> library is removed to address reported security vulnerabilities.</p></td><td><p>W-19292855</p></td></tr></tbody></table>

## 11.2.0

**August 3, 2025**

### What’s New

- Salesforce Connector now supports Salesforce API v64.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0</p></td></tr></tbody></table>

## 11.1.3

**July 12, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector no longer ignores the fields with null values in the Apex call.</p></td><td><p>W-18300119</p></td></tr></tbody></table>

## 11.1.2

**June 26, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>For the OAuth Client Credentials connection type, the connector now refreshes the token when a session expiry error is thrown.</p></td><td><p>W-18622981</p></td></tr><tr><td><p>The <code>commons-beanutils</code> dependency is upgraded to version 1.11.0 to address reported security vulnerabilities.</p></td><td><p>W-18748996</p></td></tr><tr><td><p>The <code>jetty-util-ajax</code> dependency is upgraded to version 12.0.20 to address reported security vulnerabilities.</p></td><td><p>W-18745782</p></td></tr><tr><td><p>The <code>mule-sdk-api</code> dependency is upgraded to version 0.10.5 to address reported security issues.</p></td><td><p>W-18223586</p></td></tr></tbody></table>

## 11.1.1

**May 14, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now prints an <code>INFO</code> level log entry to indicate a successful channel subscription when using the <strong>Replay Channel Subscription</strong> operation.</p></td><td><p>W-17941999</p></td></tr><tr><td><p><code>ConcurrentModificationException</code> errors no longer occur when using the <strong>Upsert</strong> operation within a <code>parallel-foreach</code> block.</p></td><td><p>W-17871379</p></td></tr><tr><td><p>The <code>allure-junit4</code> dependency is upgraded to version 2.29.1 to address reported security vulnerabilities.</p></td><td><p>W-18327105</p></td></tr><tr><td><p>The <code>commons-text</code> dependency is upgraded to version 1.12.0 to address reported security vulnerabilities.</p></td><td><p>W-18245414</p></td></tr><tr><td><p>The <code>cxf-rt-wsdl</code> dependency is upgraded to version 3.5.11 to address reported security vulnerabilities.</p></td><td><p>W-18245414</p></td></tr></tbody></table>

## 11.1.0

**April 16, 2025**

### What’s New

- Salesforce Connector now supports Salesforce API v62.0 and v63.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Replay Channel Listener</strong> source now handles disconnect messages when the servers go down.</p></td><td><p>W-16706386</p></td></tr><tr><td><p>The connector now avoids duplicate message processing by improving handling of unavailable replay ID storage in the ObjectStore during application restarts.</p></td><td><p>W-17236918</p></td></tr></tbody></table>

## 11.0.0

**March 27, 2025**

### What’s New

- The **OAuth Client Credentials** connection type is added.
- The **Subscribe Channel Listener** source is removed. Use the **Replay Channel Listener** source
  instead by using the `ONLY_NEW` replay option.
- The **Subscribe Topic Listener** source is removed. Use the **Replay Topic Listener** source
  instead by using the `ONLY_NEW` replay option.
- The deprecated **Query Result Stream** operation is removed. Use both of these operations instead:
  - The **Query Result List** operation to return a list of result IDs for a specific batch.
  - The **Query Result Stream by Id** operation to return an InputStream with the query results for
    a specific result ID of a submitted BatchInfo.

For more information about how to upgrade this connector to version 11.0.0, refer to
[Upgrading and Migrating Salesforce Connector to 11.x](../../salesforce-connector/latest/salesforce-connector-upgrade-migrate).

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.6.6 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

## 10.22.9

**March 18, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>On Modified Object</strong> source now fetches all records as intended.</p></td><td><p>W-17076953</p></td></tr></tbody></table>

## 10.22.8

**February 28, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <code>org.apache.cxf</code> library is upgraded to version 3.5.10 to address reported security vulnerabilities.</p></td><td><p>W-17734742</p></td></tr><tr><td><p>The <code>com.fasterxml.jackson.core</code> library is upgraded to version 2.16.0 to address reported security vulnerabilities.</p></td><td><p>W-17873467</p></td></tr><tr><td><p>The <code>org.eclipse.jetty</code> library is upgraded to version 9.4.57.v20241219 to address reported security vulnerabilities.</p></td><td><p>W-17873467</p></td></tr></tbody></table>

## 10.22.7

**February 20, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The refresh token is now able to start a new session in case of session expiry when using an OAuth 2.0 connection.</p></td><td><p>W-17118698</p></td></tr></tbody></table>

## 10.22.6

**February 17, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Query All</strong> operation now queries further records using the nested <code>queryLocator</code> as intended.</p></td><td><p>W-17215517</p></td></tr></tbody></table>

## 10.22.5

**January 27, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <code>/meta/connect</code> channel is updated to restart the source for <code>403::Unknown client</code> error with <code>reconnect=handshake</code> advice. This change applies to <strong>Replay Channel Listener</strong>, <strong>Replay Topic Listener</strong>, <strong>Subscribe Channel Listener</strong>, and <strong>Subscribe Topic Listener</strong> sources.</p></td><td><p>W-16878879</p></td></tr></tbody></table>

## 10.22.4

**November 5, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <code>commons-io</code> library is upgraded to version 2.16.1 to address reported security vulnerabilities.</p></td><td><p>W-17059130</p></td></tr></tbody></table>

## 10.22.3

**September 30, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Query xml stream</strong> operation now supports null value fields in the query response.</p></td><td><p>W-16425750</p></td></tr><tr><td><p>The <strong>Upsert</strong> operation now supports the Long data type in input fields.</p></td><td><p>W-16436698</p></td></tr></tbody></table>

## 10.22.2

**September 16, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <code>org.apache.cxf:cxf-rt-wsdl</code> library is upgraded to version 3.5.9 to address reported security vulnerabilities.</p></td><td><p>W-16703756</p></td></tr></tbody></table>

## 10.22.1

**August 19, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <code>org.opensaml:opensaml-saml-api</code>, <code>org.opensaml:opensaml-saml-impl</code>, and <code>org.opensaml:opensaml-core</code> libraries are upgraded to version 3.4.6 to address reported security vulnerabilities.</p></td><td><p>W-16116513</p></td></tr></tbody></table>

## 10.22.0

**August 12, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Update Metadata</strong> operation now updates the <code>valueSettings</code> metadata type as intended.</p></td><td><p>W-16213312</p></td></tr></tbody></table>

## 10.21.0

**July 12, 2024**

### What’s New

- Salesforce Connector now supports Salesforce API v61.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0</p></td></tr></tbody></table>

## 10.20.3

**June 10, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Create Metadata</strong> operation now successfully sends the ListViewFilter and SharedTo properties when creating a ListView object.</p></td><td><p>W-15957678</p></td></tr></tbody></table>

## 10.20.2

**May 14, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The session ID is no longer logged at the <code>INFO</code> level in the <strong>Replay Channel Listener</strong> and <strong>Replay Topic Listener</strong> sources.</p></td><td><p>W-15693331</p></td></tr></tbody></table>

## 10.20.1

**April 11, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now correctly parses a user entered replay ID that is greater than an integer.</p></td><td><p>W-15470844</p></td></tr></tbody></table>

## 10.20.0

**February 29, 2024**

### What’s New

- Salesforce Connector now supports Salesforce API v60.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0</p></td></tr></tbody></table>

## 10.19.4

**February 23, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now correctly processes duplicate change data capture (CDC) events when listening to enriched CDC channels.</p></td><td><p>W-15080054</p></td></tr><tr><td><p>The <strong>Query Xml Stream</strong> operation no longer fails when using the <strong>Repeatable File Store Iterable</strong> streaming strategy and a batch size is less than the page size.</p></td><td><p>W-14997923</p></td></tr><tr><td><p>The Bouncy Castle library (bcprov-jdk15on) is removed to address reported security vulnerabilities.</p></td><td><p>W-15018610</p></td></tr></tbody></table>

## 10.19.3

**January 31, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now properly supports SSL/TLS when setting up the truststore configuration in the connection configuration.</p></td><td><p>W-14910939</p></td></tr></tbody></table>

## 10.19.2

**January 8, 2024**

### What’s New

- This connector is now compatible with Java 17.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now correctly replaces the number data types in query parameters.</p></td><td><p>W-14656521</p></td></tr></tbody></table>

## 10.19.1

**December 4, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The Bouncy Castle library is upgraded to version 1.77 to address reported security vulnerabilities.</p></td><td><p>W-14508444</p></td></tr></tbody></table>

## 10.19.0

**November 13, 2023**

### What’s New

- Salesforce Connector now supports Salesforce API v59.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The Jetty Util Ajax library is upgraded to version 11.0.17 to address reported security vulnerabilities.</p></td><td><p>W-14461813</p></td></tr></tbody></table>

## 10.18.8

**November 7, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>When multiple sources are in the same channel (but in different flows) and have the <strong>Cache events in memory</strong> field enabled, the events no longer overlap.</p></td><td><p>W-14354943</p></td></tr></tbody></table>

## 10.18.7

**October 23, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>Events cached in memory when the <strong>Cache events in memory</strong> field is enabled are no longer lost. This issue was introduced in Salesforce Connector 10.18.6.</p></td><td><p>W-14346741</p></td></tr></tbody></table>

## 10.18.6

**October 19, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The OAuth access token now properly refreshes when it expires.</p></td><td><p>W-14328493</p></td></tr><tr><td><p>When the <strong>Replay failed events if any or resume from last replay id</strong> field is enabled in the streaming sources, the first failed event is no longer missed when the connector resubscribes.</p></td><td><p>W-13679492</p></td></tr><tr><td><p>The Jetty libraries are upgraded to version 9.4.53.v20231009 to address reported security vulnerabilities.</p></td><td><p>W-14287997</p></td></tr></tbody></table>

## 10.18.5

**September 22, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The streaming sources no longer process duplicate events.</p></td><td><p>W-14151797</p></td></tr></tbody></table>

## 10.18.4

**September 1, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Query</strong> operation now returns the correct values for COUNT() in SOQL.</p></td><td><p>W-14025898</p></td></tr></tbody></table>

## 10.18.3

**August 16, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The overall stability and performance of the connector are improved.</p></td><td><p>W-13625323</p></td></tr></tbody></table>

## 10.18.2

**July 17, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Query</strong> operation no longer throws <code>NoSuchElementException</code> errors when used with <strong>Batch</strong> components.</p></td><td><p>W-13759344</p></td></tr></tbody></table>

## 10.18.1

**July 11, 2023**

### What’s New

- The com.force.api:force-wsc library is upgraded to version 58.1.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The com.force.api:force-wsc library is upgraded to version 58.1.0 to address reported security vulnerabilities.</p></td><td><p>W-13545128, W-13236535</p></td></tr></tbody></table>

## 10.18.0

**June 20, 2023**

### What’s New

- Salesforce Connector now supports Salesforce API v58.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0</p></td></tr></tbody></table>

## 10.17.3

**May 11, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The org.json:json library is upgraded to version 20230227 to address reported security vulnerabilities.</p></td><td><p>W-13175461</p></td></tr></tbody></table>

## 10.17.2

**May 4, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The logging level for sources is now <code>DEBUG</code> instead of <code>INFO</code> to avoid an excess of logs.</p></td><td><p>W-13105261</p></td></tr></tbody></table>

## 10.17.1

**April 24, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Retrieve Job Failed Results Bulk V2</strong> operation no longer fails when the API response is <code>204 No-Content</code>.</p></td><td><p>W-13087981</p></td></tr></tbody></table>

## 10.17.0

**April 10, 2023**

### What’s New

- Salesforce Connector now supports Salesforce API v57.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Invoke apex rest method</strong> operation now returns the HTTP response headers.</p></td><td><p>W-12985345</p></td></tr></tbody></table>

## 10.16.9

**March 30, 2023**

### What’s New

- The commons-fileupload library is upgraded to version 1.5.0 to address reported security
  vulnerabilities.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The commons-fileupload library is upgraded to version 1.5.0 to address reported security vulnerabilities.</p></td><td><p>W-12756093</p></td></tr></tbody></table>

## 10.16.8

**March 9, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now includes enhanced error handling.</p></td><td><p>W-12584792</p></td></tr></tbody></table>

## 10.16.7

**January 26, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>Streaming sources no longer stop receiving events after consecutive network-related errors.</p></td><td><p>W-12388702</p></td></tr><tr><td><p>The Open CSV library is upgraded to version 5.7.1 to address reported security vulnerabilities.</p></td><td><p>W-12443473</p></td></tr></tbody></table>

## 10.16.6

**January 13, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Get query job results bulk api v2</strong> operation no longer has a performance issue when processing a large number of items.</p></td><td><p>W-12233199</p></td></tr><tr><td><p>The apache cxf library is upgraded to version 3.5.5 to address reported security vulnerabilities.</p></td><td><p>W-12292600</p></td></tr></tbody></table>

## 10.16.5

**December 23, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>All Bulk API v2 operations, the <strong>Push Generic Event</strong> operation, and the <strong>Invoke Apex Rest Method</strong> operation no longer incorrectly throw a <code>NullPointerException</code> when using an OAuth 2.0 connection.</p></td><td><p>W-12236769</p></td></tr></tbody></table>

## 10.16.4

**December 12, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now supports automatic type discovery for referenced fields in standard relationships.</p></td><td><p>W-12095893</p></td></tr></tbody></table>

## 10.16.3

**November 11, 2022**

### What’s New

- The org.eclipse.jetty:jetty-util-ajax library is upgraded to version 11.0.12.
- The com.fasterxml.woodstox:woodstox-core library is upgraded to version 6.4.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The org.eclipse.jetty:jetty-util-ajax library is upgraded to version 11.0.12 to address reported security vulnerabilities.</p></td><td><p>W-12029904</p></td></tr><tr><td><p>The com.fasterxml.woodstox:woodstox-core library is upgraded to version 6.4.0 to address reported security vulnerabilities.</p></td><td><p>W-11996699</p></td></tr></tbody></table>

## 10.16.2

**October 28, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now handles the <code>This session is not valid for use with the API</code> error messages correctly.</p></td><td><p>W-11964012</p></td></tr><tr><td><p>The <strong>Subscribe channel listener</strong> source can now reconnect when using an OAuth 2.0 connection.</p></td><td><p>W-11945340</p></td></tr></tbody></table>

## 10.16.1

**October 25, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The Apache Commons Text library is upgraded from <code>org.apache.commons:commons-text:1.9</code> to <code>org.apache.commons:commons-text:1.10.0</code> to fix reported security vulnerabilities.</p></td><td><p>W-11929827</p></td></tr><tr><td><p>The <strong>Replay channel listener</strong> source now honors the reconnection strategy.</p></td><td><p>W-11948533</p></td></tr></tbody></table>

## 10.16.0

**October 17, 2022**

### What’s New

- Salesforce Connector now supports Salesforce API v56.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The commons-io package is upgraded to version 2.10.0 to address reported security vulnerabilities.</p></td><td><p>W-11911808</p></td></tr></tbody></table>

## 10.15.7

**October 13, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>When using <code>AssignmentRuleHeader</code>, the connector no longer throws a <code>NullPointerException</code>.</p></td><td><p>W-11843908</p></td></tr><tr><td><p>The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.</p></td><td><p>W-11853423</p></td></tr></tbody></table>

## 10.15.6

**September 30, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Watermarks for sources now do not save as invalid in some cases.</p></td><td><p>W-11660909</p></td></tr><tr><td><p>The connector now throws the correct exception to refresh the token.</p></td><td><p>W-11768892</p></td></tr><tr><td><p>The connector no longer has the performance issue that occurred when creating objects that have reference fields to other objects.</p></td><td><p>W-11796394</p></td></tr></tbody></table>

## 10.15.5

**September 8, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector no longer escapes characters that should not be escaped when <strong>Escape characters for parameters value</strong> is enabled for the <strong>Query</strong> operation.</p></td><td><p>W-11642999</p></td></tr></tbody></table>

## 10.15.4

**August 16, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Query</strong> operation no longer throws a <code>NullPointerException</code> when a query parameter contains a null value.</p></td><td><p>W-11570436</p></td></tr><tr><td><p>The <code>INVALID_QUERY_FILTER_OPERATOR</code> Salesforce API error code is now properly handled by the connector.</p></td><td><p>W-11576556</p></td></tr></tbody></table>

## 10.15.3

**July 28, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Fixed reported security vulnerabilities by upgrading the CometD Java Client Common from <code>org.cometd.java:cometd-java-client-common:5.0.2</code> to <code>org.cometd.java:cometd-java-client-common:5.0.12</code>.</p></td><td><p>W-11472954</p></td></tr><tr><td><p>Fixed reported security vulnerabilities by upgrading the CometD Java Client Jetty from <code>org.cometd.java:cometd-java-client-http-jetty:5.0.2</code> to <code>org.cometd.java:cometd-java-client-http-jetty:5.0.12</code>.</p></td><td><p>W-11472954</p></td></tr></tbody></table>

## 10.15.2

**July 15, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Events are now delivered after exceeding the total events daily limit.</p></td><td><p>W-11401126</p></td></tr><tr><td><p>The new <strong>Triggers Query</strong> field for the <strong>On Deleted Object</strong>, <strong>On Modified Object</strong>, and <strong>On New Object</strong> sources enables you to filter the trigger results.</p></td><td><p>W-11254534</p></td></tr></tbody></table>

## 10.15.1

**July 13, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Retrieve Job Unprocessed Results Bulk V2</strong> operation no longer fails intermittently.</p></td><td><p>W-11381309</p></td></tr><tr><td><p><strong>Replay Id</strong> is now correctly picked up from Object Store for the <strong>Replay Channel Listener</strong> and <strong>Replay Topic Listener</strong> sources.</p></td><td><p>W-11381537</p></td></tr><tr><td><p>Special characters in dynamic parameters were not automatically escaped in the <strong>Query</strong>, <strong>Query All</strong>, and <strong>Query Xml Stream</strong> operations. Now, the new <strong>Escape characters for parameters value</strong> field configures this option for the <strong>Query</strong>, <strong>Query All</strong>, and <strong>Query Xml Stream</strong> operations.</p></td><td><p>W-11381560</p></td></tr></tbody></table>

## 10.15.0

**June 16, 2022**

### What’s New

- Salesforce Connector now supports Salesforce API v55.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Fixed reported security vulnerabilities by upgrading the org.json package from <code>org.json:json:20170516</code> to <code>org.json:json:20220320</code>.</p></td><td><p>W-11202569</p></td></tr></tbody></table>

## 10.14.6

**May 31, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now contains improved error message descriptions for some operations.</p></td><td><p>W-11192699</p></td></tr><tr><td><p>The connector now properly serializes some request headers.</p></td><td><p>W-11193294</p></td></tr></tbody></table>

## 10.14.5

**May 5, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector no longer fails with an <code>INVALID_SESSION_ID</code> error when using the <strong>Create Job Bulk Api V2</strong> operation.</p></td><td><p>W-11017757</p></td></tr><tr><td><p>The connector no longer ignores the <strong>Insecure</strong> parameter for the Truststore object type.</p></td><td><p>W-11074996</p></td></tr><tr><td><p>The type of the referenced object is now dynamically resolved for some object relationships.</p></td><td><p>W-11089564</p></td></tr><tr><td><p>Fixed reported security vulnerabilities by upgrading the Bouncy Castle library from <code>org.bouncycastle:bcprov-jdk15on:1.67</code> to <code>org.bouncycastle:bcprov-jdk15on:1.70</code>.</p></td><td><p>W-11007259</p></td></tr></tbody></table>

## 10.14.4

**April 12, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The connector now parses the CSV API response for the <strong>Get query job results bulk api v2</strong> operation.</p></td><td><p>W-10976121</p></td></tr></tbody></table>

## 10.14.3

**March 29, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Upgraded <code>com.fasterxml.jackson.core:jackson-databind:2.12.6</code> to <code>com.fasterxml.jackson.core:jackson-databind:2.13.2.1</code>.</p></td><td><p>W-10913689</p></td></tr></tbody></table>

## 10.14.2

**March 11, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Fixed metadata for booleans without a default.</p></td><td><p>W-10824292</p></td></tr><tr><td><p>Replacing placeholders in the query template for the <strong>Query</strong> operation works correctly on Windows.</p></td><td><p>W-10801117</p></td></tr></tbody></table>

## 10.14.1

**March 3, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Added backup key for replayId storage in the ObjectStore to avoid issues caused by application restart in CloudHub.</p></td><td><p>W-10740869</p></td></tr></tbody></table>

## 10.14.0

**February 23, 2022**

### What’s New

- Added support for Salesforce API v54.0.
- Added the **Cache events in memory** parameter for the **Replay Topic Listener** and **Replay
  Channel Listener** sources.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Added the <strong>Cache events in memory</strong> advanced option for <strong>Replay Topic Listener</strong> and <strong>Replay Channel Listener</strong> to reduce daily limit consumption.</p></td><td><p>SE-20464</p></td></tr><tr><td><p>If you delete the running app’s OAuth access token from Salesforce Session Management, the app refreshes the token without failing.</p></td><td><p>W-10742812</p></td></tr></tbody></table>

## 10.13.4

**February 4, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Upgraded <code>org.eclipse.jetty:jetty-util-ajax:9.4.33.v20201020</code> to <code>org.eclipse.jetty:jetty-util-ajax:11.0.7</code>.</p></td><td><p>CONN-10091</p></td></tr><tr><td><p>Upgraded <code>org.apache.cxf:cxf-rt-wsdl:3.4.1</code> to <code>org.apache.cxf:cxf-rt-wsdl:3.5.0</code>.</p></td><td><p>CONN-10091</p></td></tr><tr><td><p>The <strong>Update Metadata</strong> operation did not accept the address setting type in the payload.</p></td><td><p>SE-23504</p></td></tr><tr><td><p>The message source did not reconnect.</p></td><td><p>SE-24397</p></td></tr></tbody></table>

## 10.13.3

**January 17, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>When the connector was configured to use an API version older than version 47.0, the connector did not properly resolve the object types for the <strong>Create</strong>, <strong>Update</strong>, or <strong>Upsert</strong> operations.</p></td><td><p>SE-23661</p></td></tr><tr><td><p>Optimized the connector to improve its overall stability and performance.</p></td><td><p>COCN-602</p></td></tr></tbody></table>

## 10.13.2

**January 6, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Fixed reported security vulnerabilities by upgrading <code>com.fasterxml.jackson.core:jackson-databind:2.11.1</code> to <code>com.fasterxml.jackson.core:jackson-databind:2.12.6</code>.</p></td><td><p>CONN-9835</p></td></tr><tr><td><p>Fixed reported security vulnerabilities by upgrading <code>com.google.code.gson:gson:2.8.5</code> to <code>com.google.code.gson:gson:2.8.9</code>.</p></td><td><p>CONN-9661</p></td></tr><tr><td><p>Reconnection did not work for the <strong>On New Object</strong>, <strong>On Modified Object</strong>, and <strong>On Deleted Object</strong> sources.</p></td><td><p>SE-23530</p></td></tr><tr><td><p>The <strong>Update Metadata</strong> operation did not accept the address setting type in the payload.</p></td><td><p>SE-23504</p></td></tr><tr><td><p>The <strong>Invoke Apex Soap Method</strong> operation did not display metadata keys.</p></td><td><p>SE-23725</p></td></tr><tr><td><p>The <strong>Query</strong> operation threw an <code>Uncaught throwable in task PartnerConnectionPoolExpirationScheduler</code> error.</p></td><td><p>SE-23731</p></td></tr><tr><td><p>The <strong>Get Query Job Results Bulk Api V2</strong> operation retrieved results in a different order than what was created in the query.</p></td><td><p>SE-23916</p></td></tr></tbody></table>

## 10.13.1

**November 3, 2021**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>On New Object</strong> source threw a <code>SocketException</code> error while connecting to Salesforce.</p></td><td><p>SE-22906</p></td></tr><tr><td><p>The connector processed the <strong>Replay Channel Listener</strong> source multiple times.</p></td><td><p>SE-23005</p></td></tr><tr><td><p>The connector threw a <code>403:: Organization total events daily limit exceeded</code> error when there were too many clients subscribed to the same channel.</p></td><td><p>SE-23211</p></td></tr><tr><td><p>The connector did not map the <code>SERVER_UNAVAILABLE</code> error properly.</p></td><td><p>SE-23254</p></td></tr></tbody></table>

## 10.13.0

**October 19, 2021**

### What’s New

- Added support for Salesforce API v53.0.
- Added the **Query Xml Stream** operation.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The <strong>Query</strong> operation did not map the response correctly. The new <strong>Query Xml Stream</strong> operation fixes this issue. The <strong>Query</strong> operation is now deprecated.</p></div></div></td><td><div><div><p>SE-22017</p></div></div></td></tr><tr><td><div><div><p>The connector failed to handle the <code>DUPLICATES_DETECTED</code> error code in the <strong>Batch Result</strong> operation.</p></div></div></td><td><div><div><p>SE-22145</p></div></div></td></tr><tr><td><div><div><p>The <strong>Retrieve Job Failed Results Bulk V2</strong> operation did not map the response correctly.</p></div></div></td><td><div><div><p>SE-23021</p></div></div></td></tr><tr><td><div><div><p>The <strong>Invoke Apex Rest Method</strong> operation failed with a <code>SALESFORCE:INVALID_RESPONSE</code> error when the Apex method returned null.</p></div></div></td><td><div><div><p>SE-22820</p></div></div></td></tr><tr><td><div><div><p>The <strong>Invoke Apex Rest Method</strong> operation did not map the response when the response was returned as part of the responseBody property.</p></div></div></td><td><div><div><p>SE-22712</p></div></div></td></tr><tr><td><div><div><p>The <strong>Create Batch</strong> operation incorrectly mapped input CSV content that contained commas in the text.</p></div></div></td><td><div><div><p>SE-23060</p></div></div></td></tr><tr><td><div><div><p>The data stored in the ObjectStore by the connector exceeded 10 MB per key.</p></div></div></td><td><div><div><p>SE-22491</p></div></div></td></tr><tr><td><div><div><p>The <strong>Retrieve Metadata</strong> operation failed to reconnect.</p></div></div></td><td><div><div><p>SE-22886</p></div></div></td></tr><tr><td><div><div><p>The connector did not retrieve the replay ID from the ObjectStore and failed with a <code>ExpirableKey cannot be cast to java.lang.String</code> error.</p></div></div></td><td><div><div><p>SE-22908</p></div></div></td></tr><tr><td><div><div><p>The <strong>Object Type</strong> parameter for all sources displayed the object name instead of the label.</p></div></div></td><td><div><div><p>COCN-595</p></div></div></td></tr><tr><td><div><div><p>Fixed reported security vulnerabilities by updating the XMLSec library from <code>org.apache.santuario:xmlsec:2.1.4</code> to <code>org.apache.santuario:xmlsec:2.2.3</code>.</p></div></div></td><td><div><div><p>CONN-8996</p></div></div></td></tr><tr><td><div><div><p>The <strong>Replay Channel Listener</strong> source lost events when the limit exceeded.</p></div></div></td><td><div><div><p>SE-19156</p></div></div></td></tr></tbody></table>

## 10.12.4

**September 16, 2021**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>queryAll</strong> API call operation enum was missing for the <strong>Create Job</strong> operation.</p></td><td><p>SE-22711</p></td></tr><tr><td><p>Executing <strong>Bulk API v2</strong> operations using OAuth 2.0 failed.</p></td><td><p>SE-22639</p></td></tr><tr><td><p>Executing the <strong>Invoke Apex Rest Method</strong> operation using OAuth 2.0 failed.</p></td><td><p>SE-22688</p></td></tr><tr><td><p>Objects with nonunique labels were filtered from DataSense resolution.</p></td><td><p>COCN-509</p></td></tr></tbody></table>

## 10.12.3

**September 9, 2021**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>Some events were incorrectly excluded by watermark filtering in the polling sources.</p></td><td><p>COCN-446</p></td></tr><tr><td><p>The reconnection strategy did not work for push sources after the 500::Internal Server Error occurred.</p></td><td><p>SE-22542</p></td></tr></tbody></table>

## 10.12.2

**August 4, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0</p></td></tr></tbody></table>

### Fixed Issues

- The connector threw a NumberFormatException when using an empty string in proxy-related system
  properties. (SE-21968)
- The **Update** operation did not update picklist values. (SE-21243)
- Fixed reported security vulnerabilities by updating the following libraries: (CONN-8620)
  - Jetty Util `org.eclipse.jetty:jetty-util:9.4.39.v20210325` to
    `org.eclipse.jetty:jetty-util:9.4.43.v20210629`
  - Jetty HTTP `org.eclipse.jetty:jetty-http:9.4.39.v20210325` to
    `org.eclipse.jetty:jetty-http:9.4.43.v20210629`
  - Jetty Client `org.eclipse.jetty:jetty-client:9.4.39.v20210325` to
    `org.eclipse.jetty:jetty-client:9.4.43.v20210629`

## 10.12.1

**June 25, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0</p></td></tr></tbody></table>

### Fixed Issues

- The **On Deleted Object** source was not generating events. (CPLAT-1351)
- The **Create Batch** operation did not serialize null values properly. (SE-21393)

## 10.12.0

**June 11, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0</p></td></tr></tbody></table>

### New Features

- Added support for Salesforce API v52.0.

### Fixed Issues

- Salesforce Connector was not able to parse the CANNOT_EXECUTE_FLOW_TRIGGER status code returned
  from the batch job result. (SE-19814)

## 10.11.1

**June 2, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### Fixed Issues

- Optimized the connector to improve its overall stability and performance.

## 10.11.0

**May 13, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### Fixed Issues

- There was a NullPointerException while resolving metadata for an account that didn’t have a Change
  Data Capture event channel set. (CONN-8146)
- The **Query Result Stream** operation returned only the first set of results when reading the
  result of a batch query that contained multiple response IDs. Use the two new operations **Query
  Result List** and **Query Result Stream By Id** instead. The **Query Result Stream** operation is
  now deprecated. (SE-20508)
- The **On New Object** source returned only a partial amount of records when the queried item had a
  large number of records. (SE-20729)

## 10.10.7

**April 21, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### Fixed Issues

- When using the Salesforce date mapping, the mapping failed and the "Cannot coerce Object" error
  message occurred. (COCN-74)

## 10.10.6

**April 20, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### Fixed Issues

- Synchronization issue that caused data to not persist in Object Store for the **Replay Streaming
  Channel** and **Replay Topic** sources. (SE-20296)

## 10.10.5

**April 12, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### Fixed Issues

- The object types of the sources were not filtered correctly to contain only queryable objects.
  (CCONN-768)

## 10.10.4

**April 7, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### Fixed Issues

- The connector did not interpret API errors for the Query operation correctly. (SE-20227)
- Query operations that used the special character `$` in fields failed. (SE-20281)
- Made the following library updates to fix reported security vulnerabilities: (CONN-7951)
  - Commons Codec `org.eclipse.jetty:jetty-util:9.4.35.v20201120` to
    `org.eclipse.jetty:jetty-util:9.4.39.v20210325`
  - Commons Codec `org.eclipse.jetty:jetty-http:9.4.35.v20201120` to
    `org.eclipse.jetty:jetty-http:9.4.39.v20210325`
  - Commons Codec `org.eclipse.jetty:jetty-client:9.4.35.v20201120` to
    `org.eclipse.jetty:jetty-client:9.4.39.v20210325`
  - Commons Codec `org.eclipse.jetty:jetty-io:9.4.35.v20201120` to
    `org.eclipse.jetty:jetty-io:9.4.39.v20210325`

## 10.10.3

**March 23, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### Fixed Issues

- The connector reconnection mechanism for sources sometimes created the Bayeux client multiple
  times, which caused the connector to receive platform events twice. (SE-19315)
- Some internal resources were not implemented correctly, which might have resulted in higher memory
  use than in previous connector versions. (SE-18711)

## 10.10.2

**March 12, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### Fixed Issues

Fixed the issue with passing parameters that contained special characters to the Query operation.
(SE-20008)

## 10.10.1

**March 9, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### Fixed Issues

Fixed some coercion issues for the Time, Percent, and Currency field types. (CONN-682, CONN-7705)

## 10.10.0

**March 1, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### New Features

- Added the optional Assignment Rule Id field to the Create Job Bulk Api V2 operation.(SE-19721)

## 10.9.1

**February 12, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### Fixed Issues

Made the following library updates to fix reported security vulnerabilities (SE-18213):

- Commons Codec `commons-codec:commons-codec:1.14` to `commons-codec:commons-codec:1.15`
- Guava `com.google.guava:guava:19.0-jre` to `com.google.guava:guava:30.1-jre`
- Junit `junit:junit:4.12.0` to `junit:junit:4.13.1`

## 10.9.0

**February 8, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0</p></td></tr></tbody></table>

### New Features

- Added support for Salesforce API v51.0.
- The connection now supports setting a login request timeout value that forces an exception to be
  raised if the API request to obtain a session takes too long.

### Fixed Issues

- The Replay Streaming Channel source went into a resubscription loop after it encountered a
  `Buffering capacity exceeded` error. The connector now uses a streaming transformer for the events
  being processed by the source. As a result, the field used to specify the size of the event queue
  was deprecated. (SE-18873)
- Parameter values for the Search operation did not resolve properly when the search query contained
  `newline`. (SE-19254)
- The connector did not support a timeout configuration for login requests. You can now set a
  timeout for login requests by using the new Login Request Timeout field. (SE-19535)

## 10.8.2

**February 2, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0</p></td></tr></tbody></table>

### Fixed Issues

- Upgraded XMLBeans `org.apache.xmlbeans:xmlbeans:2.5.0` to `org.apache.xmlbeans:xmlbeans:3.1.0`.
  (CONN-7634)
- Parameter values for the Search operation did not resolve properly when newline was used in the
  search query. (SE-19254)

## 10.8.1

**January 20, 2021**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0</p></td></tr></tbody></table>

### Fixed Issues

- Upgraded the Object Store Connector dependency version to 1.1.6 to avoid duplicate object store
  errors in a cluster environment. (SE-18227)
- Logging for sources now identifies the target Salesforce instance. (SE-19174)
- The Query Result Stream operation failed with an Out Of Memory Error. (SE-19258)
- Parameter values for the Search operation were not resolved properly. (SE-19254)

## 10.8.0

**December 30, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0</p></td></tr></tbody></table>

### Fixed Issues

- The **List metadata** and **Read metadata** operations were not correctly managing the `Settings`
  type. (SE-18716)
- The OAuth 2.0 connection was not properly managing token expiration. (CONN-7346)
- Upgraded Apache CXF `org.apache.cxf:cxf-rt-wsdl:3.3.4` to `org.apache.cxf:cxf-rt-wsdl:3.4.1`.

## 10.7.0

**December 10, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0</p></td></tr></tbody></table>

### New Features

Improved performance when using sources with the `Continue from Last Replay Id` option. (SE-18257)

### Fixed Issues

- The connector stopped working intermittently when using a dynamic configuration. (SE-18473)
- The 'Type' parameter values were not populated for multiple operations. (SE-18912)

## 10.6.0

**November 11, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0</p></td></tr></tbody></table>

### New Features

- Added a new advanced parameter, **Throw Exception When Organization Daily Limit Exceeded**, which
  enables the connector to throw an exception if the limit is exceeded at deployment time.
- Enhanced logging messages for the Streaming sources.

### Fixed Issues

- The Query operation was not working properly when a dynamic query with more than nine parameters
  was used. (SE-18478)
- The Streaming sources were not throwing an exception when the daily API limit was exceeded, which
  is fixed with the addition of a new advanced parameter **Throw Exception When Organization Daily
  Limit Exceeded**. (SE-17568)

## 10.5.0

**October 21, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0</p></td></tr></tbody></table>

### New Features

- Added support for Salesforce API v50.0.
- The **Create job bulk api v 2** and **Create query job bulk api v 2** operations now support the
  `Sforce-Call-Options` header to specify a default namespace.
- The **Create job bulk api v 2** operation now supports the `hardDelete` value in the **Operation**
  field.
- The **Batch result stream** operation now supports specifying an output MIME type based on the
  content type provided when creating the batch.

### Fixed Issues

- The result of the **Batch result stream** operation could not be processed successfully. The new,
  optional **Output Mime Type** field fixes this issue by enabling you to specify the content type
  provided when creating the batch. (SE-17872)
- Updating a Date field value decreased the date by one day. (SE-18095)

## 10.4.4

**October 14, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0</p></td></tr></tbody></table>

### Fixed Issues

- Processing events using the Replay Channel listener or the Replay Topic listener created many
  objects in memory that were not properly cleared, which caused applications to crash. (SE-18141)

## 10.4.3

**October 6, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0</p></td></tr></tbody></table>

### Fixed Issues

- The Describe SObject operation returned a null field type for some fields. (SE-17817)
- Warning messages were displayed in the logs for an `Invalid Session ID found in SessionHeader`
  error. (SE-17784)
- Test connection was successful, even though there were handshake issues for the streaming sources.
  (SE-17680)
- Mutual TLS did not work for the streaming sources. (SE-17991)

## 10.4.2

**September 22, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0</p></td></tr></tbody></table>

### Fixed Issues

- The Create operation did not return the duplicated record ID. (SE-17697)
- The Replay topic listener and Replay channel listener sources threw Object-Store-related
  exceptions when the Resume from the Last Replay Id feature was not enabled. (CONN-6984)

## 10.4.1

**September 9, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0</p></td></tr></tbody></table>

### Fixed Issues

- Resume from the Last Replay Id feature of the Replay sources did not work in a runtime cluster.
  (SE-17312)
- Update Metadata operation failed when using a custom field. (SE-17355)

## 10.4.0

**August 31, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0</p></td></tr></tbody></table>

### New Features

- The Retrieve Job Unprocessed Results BulkV2 operation is added.
- The Retrieve Job Failed Results BulkV2 and Retrieve Job Successful Results BulkV2 operations now
  return the original fields of the records
- Logging improvements over all operations and connection types.
- Subscribe Streaming Channel and Replay Streaming Channel sources now display all types of events
  available in the configured organisation:
  - Generic Events
  - Platform Events
  - Change Data Capture Events

### Fixed Issues

- The Query Result Stream operation was returning a `ClientInputError` because of a mismatched
  content type. The optional Content Type field can now be used with this operation for jobs that
  have different content types. (SE-17310)
- Upgraded Commons Codec `commons-io:commons-io:2.5` to `commons-io:commons-io:2.7`.

## 10.3.1

**August 21, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0</p></td></tr></tbody></table>

### Fixed Issues

The issue that caused the connector to fail to reconnect and invalidated the session when using the
`Replay Channel` operation is fixed. (SE-16950)

## 10.3.0

**July 28, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0</p></td></tr></tbody></table>

### New Features

- Added support for Salesforce API v49.0.
- Added the Merge Multiple operation to enable merging up to 200 records in a single SOAP call.

### Fixed Issues

- Upgraded the following dependencies to fix vulnerability issues:
  - Commons Codec `commons-codec:commons-codec:1.13` upgraded to `commons-codec:commons-codec:1.14`

## 10.2.1

**July 1, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0</p></td></tr></tbody></table>

### Fixed Issues

- Creating objects with fields that accept array values failed. (SE-16444)
- DataSense resolution failed for objects that have relationships with other objects. (SE-16373)
- Reconnection did not work for the Invoke APEX SOAP Method operation. (SE-16419)
- The Update Metadata operation failed for the Custom Metadata Type. (SE-16074)

## 10.2.0

**June 19, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce, Salesforce Government Cloud</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0</p></td></tr></tbody></table>

### Features

- Added support for multiple keys in the JKS file specified for the SAML and JWT authentication
  mechanisms. Use the new Certificate Alias field to specify which certificate should be used.
  (CONN-6019, CONN-6020)
- Added support for custom headers for the Invoke APEX SOAP operation. (SE-15884)
- Bulk API V2 operations now return the response headers and status as message attributes.

### Fixed Issues

- \[403::Unknown client\] messages showed up in the logs. The logging level for this message is now
  debug. (SE-16152)
- For the Convert Lead operation, the ownerId field could not be specified. (SE-16169)
- The Get Query Job Results-Bulk Api v2 operation threw an OutOfMemory error. A new Max Records Per
  Page field was added to control the number of records on each page retrieved from the API.
  (SE-16298)

## 10.1.1

**May 29, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0</p></td></tr></tbody></table>

### Fixed Issues

- The Replay Channel listener input source detected an ObjectDoesNotExistException and received
  platform events multiple times. (SE-15814)
- Metadata operations failed for DocumentFolder, EmailFolder, ReportFolder, and DashboardFolder.
  (SE-16057)
- Salesforce Connector failed when used with FTP Connector. (CONN-6077)
- Upgraded the following dependency to fix vulnerability issues:

  Woodstox Core `org.bouncycastle:bcprov-jdk15on:1.60` upgraded to
  `org.bouncycastle:bcprov-jdk15on:1.65`

## 10.1.0

**April 30, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0</p></td></tr></tbody></table>

### New Features

- Added support for API v48.0.
- Added support for subscribing to these newly-added platform events: FOStatusChangedEvent,
  OrderSummaryCreatedEvent, and OrderSumStatusChangedEvent.
- Added support for using the new RecordVisibilityContext clause when using the WITH
  filteringExpression in a query.

### Fixed Issues

The following issues are fixed in this release:

- The `Get Job State Bulk Api V2` operation threw a `SALESFORCE:UNKOWN` exception when there were
  errors processing the job. The operation now returns the actual job state with all of the details
  provided by the API. (SE-15419)
- Null payload values sent to the `Invoke` Apex REST method were disregarded. A new configuration
  parameter called `Include null values` enables you to choose whether to send request parameters
  that have null values. (SE-15357)
- The `Get Query Job Results Bulk Api V2` operation did not handle pagination correctly. (SE-15726)
- The OAuth JWT connection did not support custom domains for the audience URL. A new, optional
  field called `audienceUrl` was added to support this scenario. (SE-14071)

## 10.0.2

**March 30, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### Fixed Issues

- Refactored input sources to process messages correctly and fixed the interaction with the object
  store. (CONN-5477, SE-15212, SE-15066)
- Create operations did not support Long values for the object fields. (SE-14890)
- Fixed the APEX invocation issues related to GET requests. (SE-15097 and SE-15039)
- The operations for querying job results did not parse the CSV response properly. (SE-14560)
- Upgraded the following dependencies to fix vulnerability issues:
  - Woodstox Core `com.fasterxml.woodstox:woodstox-core:5.0.3` changed to
    `com.fasterxml.woodstox:woodstox-core:6.0.0`
  - Cryptacular `org.cryptacular:cryptacular:1.1.3` changed to `org.cryptacular:cryptacular:1.1.3`

## 10.0.1

**February 25, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### Fixed Issues

- Calling the managed package Apex REST API did not work. (SE-14774)
- Enabling a reconnection strategy for the connector resulted in different behavior when using
  different runtimes. (SE-14268)
- The scheduler responsible for keeping the connection alive shut down for cached OAuth connections,
  even though the keep alive feature was enabled. (SE-14647)
- The scheduler responsible for keeping the connection alive shut down for cached Basic
  Authentication connections, even though the keep alive feature was enabled. (SE-14682)
- Upgraded some

## 10.0.0

**January 28, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### Changes

- Removed deprecated connection types
- Made the following changes to some operations:
  - Merged multiple operations into one
  - Renamed some operations and parameters
  - Changed some operation return types

- Redesigned the Replay ID functionality
- Changed the Mule TLS Context usage
- Improved the error types
- Removed the dependency on the Dozer library
- Removed the keep alive feature as a configurable option because it is no longer needed

For more information, see
[Salesforce - Upgrade and Migrate](../../salesforce-connector/latest/salesforce-connector-upgrade-migrate).

## 9.11.2

**October 14, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0</p></td></tr></tbody></table>

### Fixed Issues

- Updating a Date field value decreased the date by one day. (SE-18095)

## 9.11.1

**September 21, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0</p></td></tr></tbody></table>

### Fixed Issues

- The Create Single operation did not return the duplicated record ID. (SE-17697)
- The Delete Job Bulk V2 operation returned NULL when successful. (CONN-6618)

## 9.11.0

**August 3, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0</p></td></tr></tbody></table>

### Fixed Issues

The Invoke APEX SOAP Method operation now allows custom SOAP headers to be sent. (SE-15884)

## 9.10.2

**June 24, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0</p></td></tr></tbody></table>

### Fixed Issues

The following issues are fixed in this release:

- Reconnection was not working for the Invoke APEX SOAP Method operation. (SE-16419)
- The Update Metadata operation was failing for the Custom Metadata Type. (SE-16074)

## 9.10.1

**June 3, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0</p></td></tr></tbody></table>

### Fixed Issues

The following issues are fixed in this release:

- Logs were flooded with warning messages when the connection expired. (SE-15855)
- The Replay Channel listener input source detected an ObjectDoesNotExistException and received
  platform events multiple times. (SE-15814)

## 9.10.0

**April 29, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0</p></td></tr></tbody></table>

### New Features

- Added support for API v48.0.
- Added support for subscribing to these newly-added platform events: FOStatusChangedEvent,
  OrderSummaryCreatedEvent, and OrderSumStatusChangedEvent.
- Added support for using the new RecordVisibilityContext clause when using the WITH
  filteringExpression in a query.

### Fixed Issues

The following issues are fixed in this release:

- Reconnection failed when using the Basic Username Password authentication type. (SE-15694 and
  SE-15713)
- The Get Bulk Job State v2 operation threw a SALESFORCE:UNKOWN exception when there were errors
  processing the job. The operation now returns the actual job state with all of the details
  provided by the API. (CONN-5721)
- The connector did not honor the read timeout value set in the connection provider for the Invoke
  APEX Soap Method operation. (SE-15727)
- The Get Query Job Results Bulk Api V2 operation did not handle pagination correctly. (CONN-5931)
- Mutual authentication failed when a custom login domain was used. (SE-15552)

## 9.9.1

**April 8, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### Fixed Issues

The following issues are fixed in this release:

- The issue that caused the Invoke Apex Rest Method operation to throw an `INVALID_SESSION_ID`
  exception even though the reconnection strategy was enabled is fixed. (SE-15429)
- The Apache CXF dependency has been upgraded to version 3.3.5 to fix a security vulnerability
  issue. (SE-15353)

## 9.9.0

**March 13, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### Fixed Issues

The following issues are fixed in this release:

- The connector threw an INVALID_TYPE_ON_FIELD_IN_RECORD error when trying to create an entity that
  contained fields of type NUMBER or CURRENCY. (SE-14890)
- The OAuth JWT connection did not support custom domains for the audience URL. A new, optional
  field called audienceUrl was added to support this scenario. (SE-14071)
- The Invoke Apex Rest method failed. (SE-15039)
- Platform events did not display in the Streaming channel list of the Subscribe channel input
  source. (SE-14953)

## 9.8.5

**February 21, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### Fixed Issues

The following issues are fixed in this release:

- Salesforce Replay Channel operation failed to process headers from HTTP Response. (SE-14958)
  Changes to fix SE-13603 were reverted to fix this regression issue.
- Salesforce Replay Channel received messages that were already consumed. (SE-15005) Changes to fix
  SE-13603 were reverted to fix this regression issue.

## 9.8.4

**February 12, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### Fixed Issues

The following issues are fixed in this release:

- Refactored the mechanism interacting with Object Store to fix the issue that occurred when using
  more than one salesforce:replay-channel in an application in CloudHub, which caused a 429 status
  code. (SE-13603)
- The issue that caused Salesforce Connector 9.8.x to consume more API calls than version 9.7.x is
  fixed by caching the API response for some requests to avoid multiple calls when they are not
  needed. (SE-14655)
- The issue that caused the Salesforce Query Job results to throw an
  `ArrayIndexOutOfBoundsException` because the connector wasn’t parsing the API response properly is
  fixed. (SE-14560)
- The issue that caused the Describe object operation to return `fieldType` as null for all objects
  was fixed by mapping the API response properly. (SE-14661)
- The issue that caused calling the managed package Apex REST API not to work is fixed. (SE-14774)

## 9.8.3

**January 28, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### Fixed Issues

The following issues are fixed in this release:

- The scheduler responsible for keeping the connection alive shut down for cached OAuth connections
  even though the keep alive feature was enabled. (SE-14647)
- The scheduler responsible for keeping the connection alive shut down for cached Basic
  Authentication connections even though the keep alive feature was enabled. (SE-14682)
- The connector could not connect to Salesforce when using Mutual Authentication. (SE-14651)
- Enabling a reconnection strategy for the connector resulted in different behavior when using
  different runtimes. (SE-14268)

### Known limitations

Because the Replay Topic and Replay Channel sources use the same object store, they have the same
limitations as the object store component. For example, depending on the object store subscription
and the application throughput, you might receive related `429` (conflict) errors, such as this one:

`CloudObjectStoreException: Unable to check existence of object with key keyName in store objectoreName, status code was 429`

For more information about object store limits, see
[FAQ: Object Store v2](../../object-store/osv2-faq).

## 9.8.2

**January 23, 2020**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### Fixed Issues

The following issues are fixed in this release:

- Salesforce Connector Retrieve Metadata operation returned API version 37.0 though requesting 47.0.
  (SE-14393)
- Salesforce Connector Upsert operation not adding custom headers to SOAP call. (SE-14384)

  Custom request headers are not supported. However, accepted request headers are now being taken
  into consideration.

### Known limitations

- Because the Replay Topic and Replay Channel sources use the same object store, they have the same
  limitations as the object store component. For example, depending on the object store subscription
  and the application throughput, you might receive related `429` (conflict) errors, such as this
  one:

`CloudObjectStoreException: Unable to check existence of object with key keyName in store objectoreName, status code was 429`

For more information about object store limits, see
[FAQ: Object Store v2](../../object-store/osv2-faq).

## 9.8.1

**December 16, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### Fixed Issues

- Upsert metadata was failing for picklist values. (SE-14043)

## 9.8.0

**November 25, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0</p></td></tr></tbody></table>

### New Features

Added support for API v47.0 with new objects and the Bulk API 2.0 Query Job operation.

### Fixed Issues

- Fixed security vulnerabilities issues. (CONN-2878)
- Updated File connector dependency for the Salesforce connector to the latest version. (CONN-3078)
- Upgraded the Object Store dependency to the latest version. (CONN-3736)
- Salesforce disconnects after a few hours. When a cached connection type was used, the reconnection
  caused a running source to fail. In version 9.7.10, a fix for this issue was provided but there
  was a NullPointerException occurring when the keep alive feature parameters were empty. (SE-12904)
- Salesforce Connector relied on an outdated version of the Java module that caused compatibility
  issues with other modules. The Java module was removed from the Salesforce Connector dependencies.
  (SE-13470)
- Calls to the Salesforce Create Job Bulk v2 operation with a large volume of data caused
  `java.lang.OutOfMemoryError: Java heap space` error. This issue has been fixed by changing the
  HTTP client to the one in the Mule SDK. To enable this functionality the
  `mule.http.requestStreaming.enable property` has to be set as a VM argument.

### Known Issues

When using the Replay Topic or Replay Channel operations, if you have multiple workers deployed in
CloudHub, duplicate messages occur. You can work around this by modifying your app to screen out
duplicate messages, or you can provide an app as a receiver, and use a shared queue to pass messages
to process between workers in your app. (SE-9992)

## 9.7.10

**October 15, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0</p></td></tr></tbody></table>

### Fixed Issues

- Failed to upsert metadata. (SE-13472)
- Create operation with a parent relationship failed. (SE-12755)
- Salesforce disconnects after a few hours. When a cached connection type was used, the reconnection
  caused a running source to fail. (SE-12904)

### Known Issues

- When using the Replay Topic or Replay Channel operations, if you have multiple workers deployed in
  CloudHub, duplicate messages occur. You can work around this by modifying your app to screen out
  duplicate messages, or you can provide an app as a receiver, and use a shared queue to pass
  messages to process between workers in your app. (SE-9992)

## 9.7.9

**September 6, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0</p></td></tr></tbody></table>

### Fixed Issues

- Fixed issue with connecting to metadata operations. (CONN-3069)
- The **Invoke Apex REST API** operation calls to the Salesforce connector did not create new
  connections for each request in Mule 4. (SE-12635)

### Known Issues

When using the Replay Topic or\*Replay Channel operations, if you have multiple workers deployed in
CloudHub, duplicate messages occur. You can work around this by modifying your app to screen out
duplicate messages, or you can provide an app as a receiver, and use a shared queue to pass messages
to process between workers in your app. (SE-9992)

## 9.7.8

**August 16, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0</p></td></tr></tbody></table>

### Fixed Issues

Unauthorize operation was not working. (SE-12081)

### Known Issues

When using the **Replay Topic** or **Replay Channel** operations, if you have multiple workers
deployed in CloudHub, duplicate messages occur. You can work around this by modifying your app to
screen out duplicate messages, or you can provide an app as a receiver and use a shared queue to
pass messages to process between workers in your app. (SE-9992)

## 9.7.7

**July 24, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0</p></td></tr></tbody></table>

### Fixed Issues

- The Get Updated Objects operation did not return updated records. This was caused by the
  Salesforce API ignoring the seconds value for the API’s `startDate` and `endDate` fields. See the
  Arguments section in the Salesforce
  [getUpdated](https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_getupdated.htm)
  operation. This was fixed so that when two or more subsequent calls occur in less than a minute,
  each call after the first returns an empty array to avoid duplicates. Messages are not lost
  because the time intervals are calculated based on the first time this operation is called and
  because the API disregards the seconds value. (SE-12253)
- OAuth v2.0 failed to get the correct session and threw INVALID_SESSION_ID after being idle.
  (SE-10988)
- Upgraded the Object Store dependency to the latest version. The Salesforce connector now uses
  [Object Store connector version 1.1.3](object-store-connector-release-notes-mule-4#1-1-3)
  internally. (CONN-2519)
- Exposed the Salesforce session key from the Salesforce connector. This is now fixed and the
  session key is no longer visible in the logs. (CONN-2511)
- Not enough information was provided for errors. Exceptions had the wrong error type and errors for
  an incorrect or missing message were fixed. (CONN-1183)

### Known Issues

Salesforce connector autoreplays after restarting the application in CloudHub. (SE-9992)

## 9.7.6

**July 5, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0</p></td></tr></tbody></table>

### Features

Added support for Salesforce v46.0.

### Fixed Issues

The **Get Updated Objects** operation was not returning updated records. (SE-12253)

### Known Issues

- Salesforce connector autoreplays after restarting the application in CloudHub. (SE-9992)
- Salesforce connector OAuth v2.0 fails to get the right session and throws INVALID_SESSION_ID after
  being idle. This issue still appears for the sources and operations that use the Bulk API and the
  Apex API. (SE-10988)

## 9.7.5

**July 1, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0</p></td></tr></tbody></table>

### Features

Added support for Salesforce v44.0 and v45.0

### Known Issues

- Salesforce connector replayId feature gap between 3.x and 4.x. (SE-11258)
- Salesforce connector autoreplays after restarting the application in CloudHub. (SE-9992)
- Salesforce connector OAuth v2.0 fails to get the right session and throws INVALID_SESSION_ID after
  being idle. This issue still appears for the sources and operations that use the Bulk API and the
  Apex API. (SE-10988)
- Salesforce connector Get Updated Objects is not returning updated records. (SE-12253)

## 9.7.4

**June 26, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0</p></td></tr></tbody></table>

### Fixed Issues

- OAuth v2.0 handles the `refresh_token` value for Core API and Metadata API operations. (SE-11869)

  The affected operations are:
  - Core API operations: changeOwnPassword, convertLead, create, createMultiple, createSingle,
    delete, deleteMultiple, describeGlobal, describeSobject, findDuplicates, findDuplicatesByIds,
    getDeleted, getDeletedRange, getServerTimestamp, getSessionId, getUpdated, getUpdatedObjects,
    getUpdatedRange, getUserInfo, merge, nonPaginatedQuery, query, queryAll, querySingle,
    resetPassword, retrieve, search, setPassword, update, updateMultiple, updateSingle, upsert,
    upsertMultiple.
  - Metadata API operations: createMetadata, deleteMetadata, deployMetadata, describeMetadata,
    listMetadata, readMetadata, renameMetadata, retrieveMetadata, updateMetadata, upsertMetadata.

### Known Issues

- Salesforce connector replayId feature gap between 3.x and 4.x. (SE-11258)
- Salesforce connector autoreplays after restarting the application in CloudHub. (SE-9992)
- Salesforce connector OAuth v2.0 fails to get the right session and throws INVALID_SESSION_ID after
  being idle. This issue still appears for the sources and operations that use the Bulk API and the
  Apex API. (SE-10988)

## 9.7.3

**June 13, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0</p></td></tr></tbody></table>

### Fixed Issues

Subscribe to a filtered topic not working with v9.7.0 - The Salesforce connector now supports
subscribing to a topic using a filter with the syntax `topicName?filterKey=filterValue`. For more
information, see the Salesforce
[Filtered Subscriptions](https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/using_filtered_subscriptions.htm)
page. (SE-11869)

### Known Issues

- Salesforce connector replayId feature gap between 3.x and 4.x. (SE-11258)
- Salesforce connector autoreplays after restarting the application in CloudHub. (SE-9992)
- Salesforce connector OAuth v2.0 fails to get the right session and throws INVALID_SESSION_ID after
  being idle. This issue still appears for the sources and operations that use the Bulk API and the
  Apex API. (SE-10988)

## 9.7.2

**May 24, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0</p></td></tr></tbody></table>

### Fixed Issues

- Metadata propagation error. (SE-11757)
- Batch aggregator executed an Upsert operation and did not return the right number of failed
  records if an error occurred. (SE-10501)
- NullPointerException occurred when resolving metadata. (CONN-1938)
- OAuth v2.0 failed to get the right session and threw INVALID_SESSION_ID after being idle. This was
  fixed partially for core operations (Create, Retrieve, Upsert, Update, Merge, Delete, Convert
  Lead, Find Duplicates, and others). (SE-10988)
- Vulnerability reported for Salesforce connector 9.2.2 - Part of the vulnerabilities reported were
  fixed by upgrading the dependencies that the connector uses. (SE-9824)

  Salesforce connector 9.7.2 now supports this library upgrade:
  - Dozer `net.sf.dozer:dozer:5.5.1` changed to `com.github.dozermapper:dozer-core:6.4.1`

### Known Issues

- Salesforce connector replayId feature gap between 3.x and 4.x. (SE-11258)
- Salesforce connector autoreplays after restarting the application in CloudHub. (SE-9992)
- Salesforce connector OAuth v2.0 fails to get right session and throws INVALID_SESSION_ID after
  being idle. This issue still appears for the sources and operations that use the Bulk API and the
  Apex API. (SE-10988)

## 9.7.1

**May 23, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0</p></td></tr></tbody></table>

### Fixed Issues

- Metadata issues for sources - The DataSense keys and output were wrong in the SubscribeTopic,
  SubscribeChannel, ReplayTopic, and ReplayChannel sources. With this version, the metadata has been
  fixed. (CONN-1918)
- Duplicate values with objectType case - Issues in the input and output DataSense for different
  objects where some of the fields were duplicated. (CONN-451)
- Vulnerability reported for Salesforce connector 9.2.2 - Part of the vulnerabilities reported were
  fixed by upgrading the dependencies the connector uses. (SE-9824)

  Salesforce connector 9.7.1 now supports these library upgrades:
  - Jetty `org.eclipse.jetty:jetty-util:9.4.11.v20180605` changed to
    `org.eclipse.jetty:jetty-util:9.4.17.v20190418`.
  - Commons BeanUtils Core (`commons-beanutils:commons-beanutils-core:1.8.3`)

    > [!NOTE] The BeanShell (`org.beanshell:bsh-core:2.0b4`) and ESAPI
    > (`org.owasp.esapi:esapi:2.1.0.1`) dependencies were removed as they were no longer used.

### Known Issues

- Batch aggregator with Salesforce Connector executing an upsert operation does not return the right
  number of failed records when something went wrong. (SE-10501)
- Salesforce connector replayId feature gap between 3.x and 4.x. (SE-11258)
- Salesforce connector autoreplays after restarting the application in CloudHub. (SE-9992)

## 9.7.0

**May 3, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0</p></td></tr></tbody></table>

### New Features

Mutual TLS support - Mutual TLS support was added for all the connection providers. (CONN-1142)

### Fixed Issues

- Salesforce Subscribe topic connector is disconnected - We have upgraded the CometD library
  `org.cometd.java:cometd-java-client:3.0.10` to a newer version
  `org.cometd.java:cometd-java-client:3.1.5` per a Salesforce recommendation, otherwise there might
  be connectivity issues. Also we have fixed an issue related to "Resume from last replay Id"
  feature of the Replay Topic and Replay Channel sources where if there were no events for 24 hours
  and a connection issue appeared, the reconnection stopped working. (SE-11365)
- Salesforce connector memory leak - There was an issue in cached connection providers where some
  objects could not be cleared properly and this was leading to a memory leak. (CONN-1625)
- Vulnerability reported for Salesforce connector 9.2.2 - A part of the vulnerabilities reported
  were fixed by upgrading some of the dependencies the connector uses. (SE-9824)

  Salesforce connector 9.7.0 now supports these library upgrades:
  - OpenSAML `org.opensaml:opensaml:2.6.4` changed to `org.opensaml:opensaml-core:3.3.0`.
  - Commons HTTP Client `commons-httpclient:commons-httpclient:3.1` vulnerability removed as it was
    part of the OpenSAML dependency.

### Known Issues

- Batch aggregator with Salesforce Connector executing an upsert operation does not return the right
  number of failed records when something went wrong. (SE-10501)
- Salesforce connector replayId feature gap between 3.x and 4.x. (SE-11258)
- Salesforce connector autoreplays after restarting the application in CloudHub. (SE-9992)

## 9.6.2

**April 23, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0</p></td></tr></tbody></table>

### Fixed Issues

- Salesforce invokes Apex metadata request for each invoke. Now the connector does not fetch all the
  metadata to validate the connection, it only performs a Get Server Timstamp operation which should
  tell the app if reconnection is necessary or not. (SE-10925)
- Vulnerability reported for Salesforce connector 9.2.2. A part of the vulnerabilities reported were
  fixed by upgrading some of the dependencies the connector uses. (SE-9824)

  Salesforce connector 9.6.2 now supports these library upgrades:
  - Xalan Java (xalan:xalan:2.7.0) upgraded to 2.7.2
  - Apache Commons FileUpload (commons-fileupload:commons-fileupload:1.3.1) upgraded to 1.4
  - Xerces (xerces:xercesImpl:2.8.0) upgraded to 2.12.0
  - Jackson-Databind (com.fasterxml.jackson.core:jackson-databind:2.9.7) upgraded to 2.9.8
  - Apache Commons BeanUtils (commons-beanutils:commons-beanutils:1.7.0) upgraded to 1.9.2
  - OWASP AntiSamy (org.owasp.antisamy:antisamy:1.5.3) upgraded to 1.5.8
  - Guava: Google Core Libraries for Java (com.google.guava:guava:22.0) upgraded to 27.0.1-jre

### Known Issues

- Batch aggregator with Salesforce Connector executing an upsert operation does not return the right
  number of failed records when something went wrong. (SE-10501)
- Salesforce connector replayId feature gap between 3.x and 4.x. (SE-11258)
- Salesforce connector autoreplays after restarting the application in CloudHub. (SE-9992)

## 9.6.1

**April 11, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0</p></td></tr></tbody></table>

### Fixed Issues

- Salesforce definition for a relationship (\_\_r usage) threw error. Fixed an issue regarding
  object relationships in Salesforce. There was a bug causing troubles when creating objects with
  custom fields that had relationships to other objects. (SE-10599)
- Salesforce Connector return wrong metadata when include a subquery with a list. Fixed output
  metadata issues for the query operation when there was a subquery included to retrieve related
  objects. (SE-10255)
- Subscribe topic operation throws `Invalid SObject Type: null` error. Fixed metadata issues for the
  Subscribe Topic source. There was an exception thrown when trying to retrieve metadata for
  different object types. (CONN-1660)
- Salesforce Metadata create order issue. There was an issue with reference fields in input
  metadata, that now is fixed. (SE-10375)
- Salesforce connector create job bulk v 2 operation content type field is not valid. The only valid
  content type for this operation is CSV. We could not remove the parameter or the other content
  types, but the field was moved to the Advanced tab and a proper Summary was added for it. The
  operation is also fail fast (fails without making an API call) if a type other than CSV is
  specified. (SE-11043)
- Removed the (Deprecated) keyword in the name of the OAuth 2.0 Connection which was added by
  mistake in a previous release. The connection was not changed and can be used the same way as up
  until now.

### Known Issues

- Salesforce invokes Apex metadata request for each invoke. (SE-10925)
- Batch aggregator with Salesforce Connector executing an upsert operation does not return the right
  number of failed records when something went wrong. (SE-10501)
- Salesforce connector replayId feature gap between 3.x and 4.x. (SE-11258)
- Salesforce connector autoreplays after restarting the application in CloudHub. (SE-9992)

## 9.6.0

**March 20, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0</p></td></tr></tbody></table>

### New Features

- Added new versions of connection providers for JWT and SAML, because the existing ones do not
  match the Salesforce API behavior (one session with the same credentials at a time).

  To change an existing connection type to the new features, change the XML for the `<salesforce:`
  element as follows (in essence, add `cached-` after `salesforce:` in your XML configuration):

  <table><colgroup><col> <col></colgroup><thead><tr><th>Previous Value:</th><th>Salesforce v9.6 Value:</th></tr></thead><tbody><tr><td><p>salesforce:basic-connection</p></td><td><p>salesforce:cached-basic-connection</p></td></tr><tr><td><p>salesforce:oauth-jwt-connection</p></td><td><p>salesforce:cached-oauth-jwt-connection</p></td></tr><tr><td><p>salesforce:oauth-saml-connection</p></td><td><p>salesforce:cached-oauth-saml-connection</p></td></tr><tr><td><p>salesforce:oauth-user-pass-connection</p></td><td><p>salesforce:cached-oauth-user-pass-connection</p></td></tr><tr><td><p>salesforce:config-with-oauth-connection</p></td><td><p>No change</p></td></tr></tbody></table>

  > [!IMPORTANT] The OAuth 2.0 connection type is marked as Deprecated in Studio and Design Center,
  > however OAuth 2.0 is still available. The OAuth 2.0 "(Deprecated)" label can be ignored.

  The previous values are available but are deprecated. We recommend moving to the new versions.

### Fixed Issues

- Improved connection performance when executing operations by making better use of the Mule SDK’s
  thread pools.
- Fixed an issue where the connector was unable to handle empty body requests to Apex services.
- Fixed an issue where for the Retrieve operation when the specified ID was invalid the connector
  was trying to reconnect because of a wrong exception that was thrown.

## 9.5.2

**February 22, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

- Metadata for Apex classes didn’t work if an instance had more than 200 records. Fixed by using the
  search service to query the instance for Apex classes instead of a simple query.
- Null values were set as blank by DataWeave when obtained from the Salesforce Connector. Fixed by
  changing the returning JSONObject.NULL fields to null.
- Improved the API call that validates the connection to improve connector performance.

## 9.5.1

**February 14, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

- Invalid Session ID and Reconnection Strategy works only after multiple invalid requests when this
  connector performs a concurrent query. Fixed by implementing a new
  CachedOauthUserPassConnectionProvider with keep-alive functionality.
- GetSessionId was not returning the correct ID after the session was invalidated, because it was
  not throwing the correct exception. This was fixed by adding a call to the API, that returns a
  ConnectionException if the session ID is invalid
- The operation "Create Content Version" was failing if the payload was of binary data type. This
  was fixed by checking the data type before casting to String, so no exception is thrown
- Apex method call recognized an output field as a date if the return string has a similar format as
  Date. Methods in Apex come with a return type parameter which is now included in the condition
  which converts a string to a date type.
- Invoking Apex REST was not reconnecting when a session expired. Fixed by properly handling
  exceptions thrown by the Apex API.
- Fixed problem that occurred when attempting to create a new Content Version that had data as a
  Base64 format picture, it is not required to decode the Base64 string since the decoding is
  handled by the connector.

  This also impacts SE-9518, this fix is deprecated. Users that have VersionData that is not Base64
  must ensure that they convert it to Base64, for example: `VersionData:toBase64(payload)`

  In short, VersionData for the Version Content expects a Base64 format.

## 9.5.0

**February 1, 2019**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

- The clearNullFields config parameter was not used properly and its functionality would have never
  worked. Fixed the way clearNullFields is handled and now works as intended.
- Fixed Salesforce Connector not reconnecting when a Bulk operation session expired. Fixed by
  changing the exception thrown in this case.
- Retrieve record failure Bulk v2 not failing because of column delimiter. Fixed by adding handling
  for a column delimiter for the retrieve record failure Bulk v2.
- Invalid Session ID and Reconnection Strategy works only after multiple invalid requests when the
  Mule connector performs a concurrent query. Fixed by implementing a new
  CachedBasicConnectionProvider with keep-alive functionality.
- The BasicConnectionProvider was deprecated because a PoolingConnectionProvider does not have sense
  in the context of Salesforce’s way of handling multiple logins, which returns the same sessionId.
- Username Password connection provider was improved by handling invalid connections currently in
  the pool, so before executing an operation, the connector ensures that the operation uses a valid
  connection.

## 9.4.8

**December 12, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

Fixed an issue on the Replay Streaming Channel where the source stopped working and receiving
messages after 48 hours. Fixed by handling the DISCONNECTED state of SalesforceBayeuxClient.

## 9.4.7

**December 7, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

Fixed an issue on the Create operation that was not returning the DuplicateResults when there was a
duplicate record in the Salesforce instance. Now if the "includeRecordDetails" header is specified,
the operation returns the details about the duplicate entities.

## 9.4.6

**November 28, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

- Fixed an issue on Query operation where the connector was not able to reconnect after the session
  became invalid
- The Query operation was not handling properly the exceptions thrown by the Salesforce API.

## 9.4.5

**November 14, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

Fixed security issues regarding libraries.

## 9.4.4

**November 14, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

- Fixed an issue in the Read Metadata operation where the connector was unable to return picklist
  values.
- Fixed the problem of error message mapping in the Create Bulk v2 operation.

## 9.4.3

**November 9, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

- Fixed an issue in the Create Batch Stream operation where the connector was not able to reconnect
  after the session became invalid.
- Fixed an issue in the Query operations where the execution was stopping if the query was invalid.
  Now a proper error is raised.

## 9.4.2

**October 29, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

Fixed mapping for DescribeSObject.

## 9.4.1

**October 8, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Fixed Issues

Added missing metadata types on Metadata operations.

## 9.4.0

**September 24, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43</p></td></tr></tbody></table>

### Features

Added support for Salesforce V43.

## 9.3.5

**October 22, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0</p></td></tr></tbody></table>

### Fixed Issues

- Fixed an issue where the connector Attachments were not supporting base64 encoded body.
- Fixed an issue on create ContentVersion object that was failing because the Content Data field was
  not serialized properly.
- Fixed an issue for the Batch info list, Batch info, and Job info operations that were going into
  an infinite loop because they were defaulting to XML content type. Optional parameters were added
  so the user can specify the content type for the entity so that it will not fail any more.

## 9.3.4

**October 8, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0</p></td></tr></tbody></table>

### Fixed Issues

Added missing metadata types on Metadata operations.

## 9.3.3

**September 19, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0</p></td></tr></tbody></table>

### Fixed Issues

- Get updated objects failed with UNKNOWN error when no records were retrieved. This is no longer
  the case.
- CustomObjectTranslation was not working for the Read Metadata operation. This was fixed.

## 9.3.2

**August 30, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0</p></td></tr></tbody></table>

### Fixed Issues

Getting NullPointerException while retrieving input metadata when describing reference type objects:

```text
org.mule.runtime.api.metadata.MetadataResolvingException: Unable to resolve metadata for: Account
Caused by: java.lang.NullPointerException: Request headers cannot be null.
```

The problem was solved by reimplementing the metadata parsing for reference type objects.

Customers saw this intermittent exception:

```text
[UnexpectedErrorFault [ApiFault  exceptionCode='INVALID_SESSION_ID'
exceptionMessage='Invalid Session ID found in SessionHeader: Illegal Session.
Session not found, missing session hash: <hash>
This error usually occurs after a session expires or a user logs out.'
```

The problem was solved by adding missing error handling for reconnection due to invalid session.

## 9.3.1

**August 1, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0</p></td></tr></tbody></table>

### Fixed Issues

Salesforce connector disconnects and never connects back again. The issue was fixed by making
changes in the Reconnection Strategy.

## 9.3.0

**July 26, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0, v42.0</p></td></tr></tbody></table>

### Features

- Update the connector to support Salesforce Spring 2018 (API v42)
- Support Bulk API v2

### Fixed Issues

- After a time that the connector was not being used, customers got the following error:

  ```text
  Root Exception stack trace:
  [UnexpectedErrorFault [ApiFault exceptionCode='INVALID_SESSION_ID'
  exceptionMessage='Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session hash: jiVw2Gqdz4jdt5QfJJcVLbEHzg4NFOAPHpWosGrWyUA=
  This error usually occurs after a session expires or a user logs out.'
  ```

  The problem was solved by reimplementing reconnection strategy for paginating queries.

- The customer couldn’t make APEX call without parameters.

  The problem was solved by making APEX methods to access the objects without using them as
  parameters.

- The customer couldn’t make APEX call without parameters with array payload.

  The problem was solved by treated the lists of parameters separately.

- When using the Salesforce connector inside a batch job that uses the Batch Aggregator with the
  Upsert operation, the records were not being marked as failed or successful because the result was
  not being returned as BulkOperationResult.

  The problem was solved by adding 4 new operations for create, update, upsert, and delete that
  return BulkOperationResult.

## 9.2.2

**June 28, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0</p></td></tr></tbody></table>

### Fixed Issues

When making a call to a Salesforce Apex method, if the method didn’t have a parameter, Salesforce
connector did not pass the flow payload to the Apex method. Now, the connector passes the flow
payload.

## 9.2.1

**May 18, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0</p></td></tr></tbody></table>

### Fixed Issues

Salesforce connector was not working in EU. When using Salesforce Connector in EU, it threw this
exception:

```text
Caused by: org.springframework.beans.factory.BeanCreationException:
Could not autowire field: private org.mule.runtime.api.store.ObjectStoreManager
org.mule.extension.salesforce.internal.operation.UtilityOperations.objectStoreManager;
nested exception is org.springframework.beans.factory.NoUniqueBeanDefinitionException:
No qualifying bean of type [org.mule.runtime.api.store.ObjectStoreManager] is defined:
expected single matching bean but found 2: _muleObjectStoreManager,_muleLocalObjectStoreManager
```

In this version Salesforce Connector works correctly in EU.

## 9.2.0

**May 2, 2018**

### Compatibility

Salesforce connector version 9.2.0 is compatible with:

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.0 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0</p></td></tr></tbody></table>

### Features

- Changed Minimum Mule Version to 4.1.1.

## 9.1.2

**May 18, 2018**

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.0 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0</p></td></tr></tbody></table>

### Fixed Issues

Salesforce connector was not working in EU. When using Salesforce Connector in EU, it threw this
exception:

```text
Caused by: org.springframework.beans.factory.BeanCreationException:
Could not autowire field: private org.mule.runtime.api.store.ObjectStoreManager
org.mule.extension.salesforce.internal.operation.UtilityOperations.objectStoreManager;
nested exception is org.springframework.beans.factory.NoUniqueBeanDefinitionException:
No qualifying bean of type [org.mule.runtime.api.store.ObjectStoreManager] is defined:
expected single matching bean but found 2: _muleObjectStoreManager,_muleLocalObjectStoreManager
```

In this version Salesforce Connector works correctly in EU.

## 9.1.1

**May 2, 2018**

### Compatibility

Salesforce connector version 9.1.1 is compatible with:

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.0 and later</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0</p></td></tr></tbody></table>

### Features

- Added the isForceResubscribe method in Salesforce Bayeux Client.
- Support for Anypoint Studio Proxy configuration as the default.

### Fixed Issues

- Trigger operation did not retrieve MetadataKeysId. Solved by adding support for retrieving
  metadata in case of sources.
- Reply topic was losing messages in case the connection has been lost for less than 40 seconds;
  this is the amount of time that was needed to trigger re-subscribe naturally according to
  Salesforce documentation. The issue was solved by forcing re-subscription whenever the network
  connection is lost.
- Buffering capacity exceeded message was triggered when the connector consumed more than 10000
  messages from a topic. The issue was solved by adding a new attribute for the "Replay streaming
  channel" operation: Buffer Size In Bytes, it’s an optional parameter with the default value of 26
  MB.
- Wrong transformation of fields of type Date. Trying to update or insert an Object in Salesforce
  with fields of type Date caused a failure, this was due to failure in serializing the objects of
  type Date. The issue was solved by parsing the values received from the Mule flow and converting
  them into the expected Salesforce accepted format.

## 9.1.0

**February 21, 2018**

This release adds new features.

### Compatibility

Salesforce connector version 9.1.0 is compatible with:

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.0</p></td></tr><tr><td><p>Salesforce</p></td><td><p>v37.0, v38.0, v39.0, v40.0, v41.0</p></td></tr></tbody></table>

### Features

- Support for new and changed objects in metadata - API v41.
- Support for defining any absolute path for the keystore.
- Salesforce trigger - To address ad-hoc integrators or citizen integrators with Design Center, you
  can now start a flow with the Salesforce connector when you create an object. For example, when
  new data is added to a lead object or an opportunity object, you now have an easier way to
  initiate a flow.

### Fixed Issues

Query with parameters didn’t work.

## See Also

- [Salesforce Help](https://help.salesforce.com)
- [MuleSoft Services](https://www.mulesoft.com/support-and-services)
- [Known Issues](https://help.salesforce.com/s/issues)