Contact Us 1-800-596-4880

Salesforce Connector Release Notes - Mule 4

Support Category: Select

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

10.15.5

September 8, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

The connector no longer escapes characters that should not be escaped when Escape characters for parameters value is enabled for the Query operation.

W-11642999

10.15.4

August 16, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

The Query operation no longer throws a NullPointerException when a query parameter contains a null value.

W-11570436

The INVALID_QUERY_FILTER_OPERATOR Salesforce API error code is now properly handled by the connector.

W-11576556

10.15.3

July 28, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

Fixed reported security vulnerabilities by upgrading the CometD Java Client Common from org.cometd.java:cometd-java-client-common:5.0.2 to org.cometd.java:cometd-java-client-common:5.0.12.

W-11472954

Fixed reported security vulnerabilities by upgrading the CometD Java Client Jetty from org.cometd.java:cometd-java-client-http-jetty:5.0.2 to org.cometd.java:cometd-java-client-http-jetty:5.0.12.

W-11472954

10.15.2

July 15, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

Events are now delivered after exceeding the total events daily limit.

W-11401126

The new Triggers Query field for the On Deleted Object, On Modified Object, and On New Object sources enables you to filter the trigger results.

W-11254534

10.15.1

July 13, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

The Retrieve Job Unprocessed Results Bulk V2 operation no longer fails intermittently.

W-11381309

Replay Id is now correctly picked up from Object Store for the Replay Channel Listener and Replay Topic Listener sources.

W-11381537

Special characters in dynamic parameters were not automatically escaped in the Query, Query All, and Query Xml Stream operations. Now, the new Escape characters for parameters value field configures this option for the Query, Query All, and Query Xml Stream operations.

W-11381560

10.15.0

June 16, 2022

What’s New

  • Salesforce Connector now supports Salesforce API v55.0.

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

Fixed reported security vulnerabilities by upgrading the org.json package from org.json:json:20170516 to org.json:json:20220320.

W-11202569

10.14.6

May 31, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

The connector now contains improved error message descriptions for some operations.

W-11192699

The connector now properly serializes some request headers.

W-11193294

10.14.5

May 5, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

The connector no longer fails with an INVALID_SESSION_ID error when using the Create Job Bulk Api V2 operation.

W-11017757

The connector no longer ignores the Insecure parameter for the Truststore object type.

W-11074996

The type of the referenced object is now dynamically resolved for some object relationships.

W-11089564

Fixed reported security vulnerabilities by upgrading the Bouncy Castle library from org.bouncycastle:bcprov-jdk15on:1.67 to org.bouncycastle:bcprov-jdk15on:1.70.

W-11007259

10.14.4

April 12, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

The connector now parses the CSV API response for the Get query job results bulk api v2 operation.

W-10976121

10.14.3

March 29, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

Upgraded com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.13.2.1.

W-10913689

10.14.2

March 11, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

Fixed metadata for booleans without a default.

W-10824292

Replacing placeholders in the query template for the Query operation works correctly on Windows.

W-10801117

10.14.1

March 3, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

Added backup key for replayId storage in the ObjectStore to avoid issues caused by application restart in CloudHub.

W-10740869

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

Added the Cache events in memory advanced option for Replay Topic Listener and Replay Channel Listener to reduce daily limit consumption.

SE-20464

If you delete the running app’s OAuth access token from Salesforce Session Management, the app refreshes the token without failing.

W-10742812

10.13.4

February 4, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

Upgraded org.eclipse.jetty:jetty-util-ajax:9.4.33.v20201020 to org.eclipse.jetty:jetty-util-ajax:11.0.7.

CONN-10091

Upgraded org.apache.cxf:cxf-rt-wsdl:3.4.1 to org.apache.cxf:cxf-rt-wsdl:3.5.0.

CONN-10091

The Update Metadata operation did not accept the address setting type in the payload.

SE-23504

The message source did not reconnect.

SE-24397

10.13.3

January 17, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

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 Create, Update, or Upsert operations.

SE-23661

Optimized the connector to improve its overall stability and performance.

COCN-602

10.13.2

January 6, 2022

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

Fixed reported security vulnerabilities by upgrading com.fasterxml.jackson.core:jackson-databind:2.11.1 to com.fasterxml.jackson.core:jackson-databind:2.12.6.

CONN-9835

Fixed reported security vulnerabilities by upgrading com.google.code.gson:gson:2.8.5 to com.google.code.gson:gson:2.8.9.

CONN-9661

Reconnection did not work for the On New Object, On Modified Object, and On Deleted Object sources.

SE-23530

The Update Metadata operation did not accept the address setting type in the payload.

SE-23504

The Invoke Apex Soap Method operation did not display metadata keys.

SE-23725

The Query operation threw an Uncaught throwable in task PartnerConnectionPoolExpirationScheduler error.

SE-23731

The Get Query Job Results Bulk Api V2 operation retrieved results in a different order than what was created in the query.

SE-23916

10.13.1

November 3, 2021

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

The On New Object source threw a SocketException error while connecting to Salesforce.

SE-22906

The connector processed the Replay Channel Listener source multiple times.

SE-23005

The connector threw a 403:: Organization total events daily limit exceeded error when there were too many clients subscribed to the same channel.

SE-23211

The connector did not map the SERVER_UNAVAILABLE error properly.

SE-23254

10.13.0

October 19, 2021

What’s New

  • Added support for Salesforce API v53.0.

  • Added the Query Xml Stream operation.

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

The Query operation did not map the response correctly. The new Query Xml Stream operation fixes this issue. The Query operation is now deprecated.

SE-22017

The connector failed to handle the DUPLICATES_DETECTED error code in the Batch Result operation.

SE-22145

The Retrieve Job Failed Results Bulk V2 operation did not map the response correctly.

SE-23021

The Invoke Apex Rest Method operation failed with a SALESFORCE:INVALID_RESPONSE error when the Apex method returned null.

SE-22820

The Invoke Apex Rest Method operation did not map the response when the response was returned as part of the responseBody property.

SE-22712

The Create Batch operation incorrectly mapped input CSV content that contained commas in the text.

SE-23060

The data stored in the ObjectStore by the connector exceeded 10 MB per key.

SE-22491

The Retrieve Metadata operation failed to reconnect.

SE-22886

The connector did not retrieve the replay ID from the ObjectStore and failed with a ExpirableKey cannot be cast to java.lang.String error.

SE-22908

The Object Type parameter for all sources displayed the object name instead of the label.

COCN-595

Fixed reported security vulnerabilities by updating the XMLSec library from org.apache.santuario:xmlsec:2.1.4 to org.apache.santuario:xmlsec:2.2.3.

CONN-8996

The Replay Channel Listener source lost events when the limit exceeded.

SE-19156

10.12.4

September 16, 2021

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

The queryAll API call operation enum was missing for the Create Job operation.

SE-22711

Executing Bulk API v2 operations using OAuth 2.0 failed.

SE-22639

Executing the Invoke Apex Rest Method operation using OAuth 2.0 failed.

SE-22688

Objects with nonunique labels were filtered from DataSense resolution.

COCN-509

10.12.3

September 9, 2021

Compatibility

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

Issue ID

Some events were incorrectly excluded by watermark filtering in the polling sources.

COCN-446

The reconnection strategy did not work for push sources after the 500::Internal Server Error occurred.

SE-22542

10.12.2

August 4, 2021

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

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

10.11.0

May 13, 2021

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

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

10.10.1

March 9, 2021

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

Fixed Issues

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

10.10.0

March 1, 2021

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

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

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

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.

9.11.2

October 14, 2020

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0

Fixed Issues

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

9.11.1

September 21, 2020

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0

Fixed Issues

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

9.10.2

June 24, 2020

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

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.

9.8.2

January 23, 2020

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

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.

9.8.1

December 16, 2019

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

Fixed Issues

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

9.8.0

November 25, 2019

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0

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)

      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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0

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

    Previous Value: Salesforce v9.6 Value:

    salesforce:basic-connection

    salesforce:cached-basic-connection

    salesforce:oauth-jwt-connection

    salesforce:cached-oauth-jwt-connection

    salesforce:oauth-saml-connection

    salesforce:cached-oauth-saml-connection

    salesforce:oauth-user-pass-connection

    salesforce:cached-oauth-user-pass-connection

    salesforce:config-with-oauth-connection

    No change

    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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

Fixed Issues

Fixed security issues regarding libraries.

9.4.4

November 14, 2018

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

Studio 7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

Fixed Issues

Fixed mapping for DescribeSObject.

9.4.1

October 8, 2018

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

Fixed Issues

Added missing metadata types on Metadata operations.

9.4.0

September 24, 2018

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43

Features

Added support for Salesforce V43.

9.3.5

October 22, 2018

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0

Fixed Issues

Added missing metadata types on Metadata operations.

9.3.3

September 19, 2018

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0

Fixed Issues

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

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:

[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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0

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:

    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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0

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

Application/Service Version

Mule

4.1.1 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0

Fixed Issues

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

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:

Application/Service Version

Mule

4.1.0 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0

Features

  • Changed Minimum Mule Version to 4.1.1.

9.1.2

May 18, 2018

Application/Service Version

Mule

4.1.0 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0

Fixed Issues

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

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:

Application/Service Version

Mule

4.1.0 and later

Anypoint Studio

7.1.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0

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:

Application/Service Version

Mule

4.1.0

Anypoint Studio

7.0.0 and later

Salesforce

v37.0, v38.0, v39.0, v40.0, v41.0

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.