Nav

Salesforce Connector Release Notes

July 21, 2017

Guide:

Starting with v.6.0.2, the Salesforce Connector is licensed commercially with Anypoint Platform as with other Select connectors. Prior versions will remain freely available to the community.

Version 9.0.0 Compatibility

Application/Service Version

Mule Runtime

Mule Enterprise Edition 4.0.0 and newer

Anypoint Studio

Only works with Studio 7.0.0 and newer

Salesforce

v37.0, v38.0, v39.0

Version 9.0.0 Known Issues

  • While an array of objects is returned for a set of operations, metadata shows the response as an object.

Salesforce Connector 8.3.1 - July 3, 2017

Salesforce connector version 8.3.1 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v37.0, v38.0, v39.0

Version 8.3.1 - Fixed in this Release

  • Failure to refresh metadata: In the previous version Refresh Metadata failed when references (__r) were used in a SELECT statement. Currently statements like: `SELECT a.OtherObject_r.CustomFieldc FROM MyCustomObject_c a' should work.

  • Salesforce topic subscription failure with API v37 v38 and v39: In previous version/s, in long-running salesforce applications subscribed to a topic it throwed a org.cometd.3_0_10.shade.common.TransportException: {httpCode=404}. Currently, after a proper configuration, topic subscription shouldn’t fail after a long-running. Check User Manual - Subscribing to a Topic

Salesforce Connector 8.3.0 - April 17, 2017

Salesforce connector version 8.3.0 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v37.0, v38.0, v39.0

Version 8.3.0 Features

  • Added support for salesforce API v39.0

  • Added support for the "WITH HIGHLIGHT" operator in the Query All operation

Version 8.3.0 - Fixed in this Release

  • Content Type is now supported in the Create Job operation.

Salesforce Connector 8.2.1 - March 10, 2017

Version 8.2.1 Compatibility

Salesforce connector version 8.2.1 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v37.0, v38.0

Version 8.2.1 - Fixed in this Release

  • In the previous version 8.2.0, the name of the parameter given to operations that were expecting an object of type BatchInfo as input was changed from batch-info to batch-to-retrieve, which affected existing apps using those operations. In version 8.2.1 batch-to-retrieve has been changed back to batch-info and batch-to-retrieve has been removed.

Example of operation using batch-to-retrieve:


          
       
1
2
3
<sfdc:batch-info config-ref="Salesforce__Basic_Authentication" doc:name="Salesforce">
    <sfdc:batch-to-retrieve ref="#[payload]"/>
</sfdc:batch-info>

In version 8.2.1, this operation has been changed back to how it was in the past:


          
       
1
2
3
<sfdc:batch-info config-ref="Salesforce__Basic_Authentication" doc:name="Salesforce">
    <sfdc:batch-info ref="#[payload]"/>
</sfdc:batch-info>

Salesforce Connector 8.2.0 - March 2, 2017

Version 8.2.0 Compatibility

Salesforce connector version 8.2.0 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v37.0, v38.0

Version 8.2.0 Features

  • Added new configuration which is using OAuth2.0 Username-Password authentication flow, see: Username-Password OAuth Authentication Flow.

  • Added support for providing custom headers in the Create Job operation that provides behavior similar to "PK Chunking", see: PK Chunking Header.

  • Added support for providing custom headers on Query Result Stream that lets you set headers on request. This can be useful if you want, for example, to receive data in GZIP format by adding "Accept-Encoding=GZIP" as a header.

  • Added support for providing custom headers on Batch Result Stream that lets you set headers on request. This can be useful if you want, for example, to receive data in GZIP format by adding "Accept-Encoding=GZIP" as a header.

Version 8.2.0 - Fixed in this Release

  • When the connector was used as an inbound endpoint in case of a session expiration, it wasn’t able to refresh the session, but now is fixed.

Salesforce Connector 8.1.0 - December 2, 2016

Version 8.1.0 Compatibility

Salesforce connector version 8.1.0 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v37.0, v38.0

Version 8.1.0 Features

  • Added a new Salesforce header to the list of headers, which is DuplicateRuleHeader, that are accepted by create(), update(), upsert() and from now on, by findDuplicates()

  • Added support for find duplicates API core call. See: Find Duplicates Core Call

  • Added enhancements to the Streaming API. The connector stores the replay ID for the last processed event. The user now has the possibility to replay all unprocessed events within the 24 hour time-frame provided by Salesforce. The replay ID can now be specified as a MEL expression.

  • Added support for Batch Info List bulk API call. See: Get Information for All Batches in a Job

  • From now on, exception is thrown instead of hanging when a header from response is not recognized. (For example, for this use case: when a proxy is altering response from Salesforce.)

  • Proxy configuration was not taken in consideration by streaming inbound endpoints, fixed it.

  • When domain name was containing word "services" (for example, https://services--dev.salesforce.com/services/c/38.0) the computation of service endpoint to which upcoming requests are send was wrong, so it was fixed.

Version 8.1.0 Known Issues

  • "Resume from the last replay id” won’t work on Cloudhub because the persistent object store is not supported by Cloudhub.

Version 8.1.0 Migration Guide

Salesforce API v38 brings several API and Metadata API changes, as they are documented in the Salesforce release notes:

Salesforce Connector 8.0.0 - October 26, 2016

Version 8.0.0 Compatibility

Salesforce connector version 8.0.0 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v37.0

Version 8.0.0 Features

  • Added Generic Streaming support

  • Added support for record-related events replay through Salesforce Streaming API.

Version 8.0.0 - Fixed in this Release

  • Improved Apex classes parsing grammar

Version 8.0.0 Migration Guide

Salesforce API v37 brings several API and Metadata API changes, as they are documented in the Salesforce release notes:

When migrating to version 8.0.0, you should consider the following changes:

  • the ChildRelationship SObject field junctionIdListName has become junctionIdListNames in API v37 and has changed type from String to String[]

Salesforce Connector 7.2.0 - August 23, 2016

Version 7.2.0 Compatibility

Salesforce connector version 7.2.0 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v32.0 to v37.0

Version 7.2.0 Features

  • Added SocketException and ConnectException to ReconnectionStrategy triggers.

  • Added a new checkbox to the configuration, allowing a user to clear fields that have a null value, without using fieldsToNull list.

  • Added new icons for the Studio Light Theme.

  • When fetching the metadata for Apex Rest Classes, if an exception is thrown for an Apex Class, the metadata is fetched for the other Apex classes, and that exception will be logged. A MetadataKey is created for that Apex Class that presents the exception message.

Version 7.2.0 - Fixed in this Release

  • Reconnection Strategy now works if the session was invalidated when invoking an Apex Rest Class.

  • Corrected an issue that caused Salesforce Connector to fail in extracting the access token from the Salesforce Oauth response.

  • Now all 2xx HTTP status code responses are treated as success.

  • Corrected issues which caused some Apex Rest classes to be parsed incorrectly by the connector.

Salesforce Connector 7.1.2 - June 3, 2016

Version 7.1.2 Compatibility

Salesforce connector version 7.1.2 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v32.0 to v36.0

Version 7.1.2 - Fixed in this Release

Support for TLS version configuration for JWT, SAML authentications. It can be specified same way as for JVM by adding "https.protocols" VM option (e.g. -Dhttps.protocols=TLSv1.1,TLSv1.2)

Salesforce Connector 7.1.1 - April 25, 2016

Version 7.1.1 Compatibility

Salesforce connector version 7.1.1 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v32.0 to v36.0

Version 7.1.1 - Fixed in this Release

  • Fixed an issue regarding the dependencies used by the connector.

Salesforce Connector 7.1.0 - April 13, 2015

Version 7.1.0 Compatibility

Salesforce connector version 7.1.0 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v32.0 to v36.0

Version 7.1.0 Features

  • The connector now supports versions 32.0 to 36.0 of the Salesforce API.

  • Now the connector supports a trial version. This means that Salesforce Connector can be used with an evaluation/trial license for Mule EE

  • Added JSON support for Bulk API operations

  • Validate Configuration can now verify if the current session is valid

  • Validations are performed on Invoke Apex Rest Method to verify that restMethodName has the expected format

Version 7.1.0 Fixed in this Release

  • Fixed issue where Invoke Apex Soap Method sometimes failed to transform the result, returning null or an empty array instead.

  • When querying for attachments, the body is now properly returned as a byte array, rather than Base64.

  • Fixed issue where Batch Commit was incorrectly reporting that all records were successfully upserted although some actually failed.

  • Default input value for Batch Result, Batch Result Stream, Query Result Stream and Batch Info is now correctly set to payload.

  • Multiple flows can now subscribe to the same Topic, fixing an issue where only one flow would actually subscribe.

Salesforce Connector 7.0.1 - December 9, 2015

Version 7.0.1 Compatibility

Salesforce connector version 7.0.1 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v32.0 to v34.0

Version 7.0.1 Fixed in this Release

  • Fixed how the way query results are returned. Exceptions related to "No converter found!" are no longer thrown for inner selects (for child relationships).

  • Because the converters introduced a huge impact on production performance it was decided that all fields are to be returned as Strings and DataWeave will be used for data transformation.

  • Batch Operation Results are reported correctly now, if Batch Commit component is used. Before the connector had problems reporting how many records were successful and how many where failed (all the recors were reported as successful).

  • Invocation of Apex Rest methods that are void no longer fails.

Version 7.0.1 Known Issues

  • Batch Operation Results report all records as successful when the Batch Commit component is not used (only the Batch Step component is used).

Salesforce Connector 7.0.0 - December 1, 2015

Version 7.0.0 Compatibility

Salesforce connector version 7.0.0 is compatible with:

Application/Service Version

Mule Runtime

Mule Enterprise Edition 3.5.2 and newer

Anypoint Studio

Only works with Studio 5.4.0 and newer

Salesforce

v32.0 to v34.0

This is a major version change, hence the connector might break backward compatibility for some existing flows. It uses DevKit 3.7 and its new features (like multi-level Datasense for invokeApexSoapMethod and invokeApexRestMethod) and dates are no longer passed as String, but as Dates and Calendars. To see how the new metadata key ids are formed for invokeApexSoapMethod and invokeApexRestMethod please read below.

Version 7.0.0 Features

  • The connector now supports versions 32.0 to 34.0 of the Salesforce API.

  • get-session-id

    • Added an extra optional input parameter to this operation, that forces the session validation.

  • describe-global and describe-sobject

    • Added an extra optional parameter to these operations in order to add Salesforce SOAP headers on the requests.

  • invoke-apex-rest-method

    • Added support for Custom Types and Apex Custom Types

    • Added multilevel Datasense (the user has to choose the Apex Class first and then in a following parameter, the user must choose a Method Name from the ones available for that class)

    • The resulting metadata key id will have the following format: 'apexClassName||apexMethodName^resourceUrl^httpMethod^outputType^inputParameters' where

      • apexClassName is the value chosen by the user for the "Apex Class" parameter under the General section of the connector tab;

      • apexMethodName is the value chosen by the user for the "Method Name" parameter under this General section;

      • resourceUrl is the value of urlMapping attribute from the '@RestResource' annotation of the apex class;

      • httpMethod is the http method annotation of the Apex Rest resource (e.g. @HttpGet, @HttpPost) without the '@' symbol;

      • outputType is the method output type (e.g. 'List<Account>');

      • inputParameters is a comma separated list of input parameters (their name and their type - e.g. 'account=Account, someParameter=String');

      • '||' is a separator used between the class name and the method name;

      • '^' is a separator for the method details.

  • invoke-apex-soap-method

    • Added multilevel Datasense (the user has to choose the Apex Class first and then in a following parameter, the user must choose a Method Name from the ones available for that class)

    • The resulting metadata key ID will have the following format: 'apexClassName||apexMethodName' where:

      • apexClassName is the value chosen by the user for the "Apex Class" parameter under the General section of the connector tab;

      • apexMethodName is the value chosen by the user for the "Method Name" parameter under this General section;

      • '||' is a separator used between the class name and the method name.

  • Changed Test Connection to Validate Configuration and added a validation for Apex Classes and Proxy configurations if these are set in the connector configuration.

  • merge

    • This is a new operation to support merging of accounts.

  • reset-password

    • This is a new operation to offer support to users wanting to reset their password through the connector.

  • Added the ability to use external IDs in metadata (DataMapper or DataWeave).

  • Added support for List<String> for fieldsToNull.

Version 7.0.0 Fixed in this Release

  • Changed the creation of the URLs used for Apex SOAP and Apex REST requests, in order to support reverse proxies.

  • Modified some Java documentation that incorrectly appeared as explanations in Studio elements like configurations.

  • Corrected the parsing of dates from Apex REST invocation responses.

  • Added validation for the existence of IDs when using the retrieve operation, to avoid possible exception thrown when it is called.

  • Dates are now returned as Calendars rather than Strings, for easier use (comparison or alteration).

  • Fixed issue with Apex REST URL not supporting certain characters like period ('.').

  • Improved overall performance for Apex REST invocation by avoiding the download and parsing of the Apex REST class at every invocation; instead we are relying on the information obtained during Datasense and data stored in the metadata key id related to the method to be invoked.

  • Removed default proxy port from the configuration as it is confusing.

  • Handle the Salesforce Address type as an object in metadata rather than a String, as before.

Version 7.0.0 Known Issues

  • This version of the connector breaks backward compatibility:

    • the way some metadata key ids are created was changed due to some performance enhancements (invokeApexSoapMethod and invokeApexRestMethod are affected by this).

    • the way the connector works with Dates has been changed: dates are no longer expected/returned as Strings; they are used as Dates or Calendars, for easier use (comparison and calculations), depending on their types.

  • Salesforce has a know issue with creating correct WSDLs for the Apex SOAP classes created under version 34.0 and 35.0 of the API. As a workaround Salesforce suggested that the Apex SOAP classes should be created under version 32.0 to be able to use them.

  • For versions v28.0, v29.0 of the Salesforce API use version v5.4.12 of the connector.

Salesforce Connector 6.2.3 - July 23, 2015

Version 6.2.3 Fixed in This Release

  • Fixed an error where session expiration would not be handled correctly even with a reconnection strategy set, in operations that returned a SalesforcePagingDelegate (query, queryall).

Salesforce Connector 6.2.2 - July 22, 2015

Version 6.2.2 Fixed in This Release

  • A bug that logged warning messages as errors once a session expired even if you had reconnection on has been fixed.

  • Support for session concurrency in multi-threaded applications has now been improved.

Salesforce Connector 6.2.1 - June 19, 2015

Version 6.2.1 Compatibility

Salesforce connector version 6.2.1 is compatible with:

Application/Service Version

Mule Runtime

3.5.2 and newer

Salesforce

v31.0 to v32.0

Version 6.2.1 Migrating From Older Versions of the Connector

If you’re using an older version of the connector, a small popup appears in the bottom right corner of Anypoint Studio that says Updates Available.

  1. Click that popup and check for available updates.

  2. Click the Salesforce Connector version 6.2.1 checkbox, click Next, and follow the instructions provided by the user interface.

  3. Restart Studio.

  4. After the restart, when creating a flow and using the Salesforce Connector, if you have several versions of the connector installed, you might be asked which version you would like to use. Select the version you would like to use.

  5. Keep Mule and Studio updated.

Version 6.2.1 Fixed in this Release

  • IDENTITY_URL_TEMPLATE hardcoded to login.salesforce.com breaks sandbox requests - there was no way of differentiating the test sandbox from the production environment (this is done through the URL the user is logged in to). Renamed in the SalesforceBasicAuthConfig the parameter URL to Authentication Url

  • Added to JWT and SAML configurations the parameter Token Endpoint ObjectStore callback attributes are not properly loaded - fields instanceId , userId , and accessToken were renamed

  • Re-added fields instanceId, userId, and accessToken taken from ObjectStore provided by user

  • "remoteUserId" variable is not set any more in the postAuthorize Re-added the remoteUserId flow variable in postAuthorize

Version 6.2.1 Known Issues

  • Connector v6.2.1 does not work with versions v28.0, v29.0, and v30.0 of the Salesforce API.

  • Connector v6.2.1 does not support for Apex Rest the following data types:

    • Custom Types

    • Lists of Lists or Maps

    • Maps of Lists or Maps

    • Object (not able to perform DataSense on it)

    • Blob (not supported by Salesforce Rest methods as input/output)

  • For versions v28.0, v29.0 of the Salesforce API use version v5.4.12 of the connector.

Salesforce Connector 6.2.0 - June 9, 2015

Version 6.2.0 Compatibility

Salesforce connector 6.2.0 is compatible with:

Application/Service Version

Mule Runtime

3.5.2 or newer

Salesforce

v31.0 to v32.0

Version 6.2.0 Updating to Version 6.2.0 of the Connector

When a new version of a connector is released, Anypoint studio displays a popup in the bottom right corner of you screen with the following message: Updates Available.

To upgrade to the newer version of the Salesforce connector:

  1. Click the popup and check for the available updates.

  2. Select the Salesforce connector 6.2 checkbox and click Next.

  3. Follow the instructions provided by the user interface.

  4. Restart Studio when prompted.

  5. After restarting, if you have several versions of the connector installed, Mule asks you for the version of the connector you like to use.

Version 6.2.0 Features

  • Salesforce APEX REST API: The connector now supports the following Apex operation:

    • Invoke Apex Rest method: Lets you invoke an operation from an Apex class that has previously been created in your organization. The operations from the Apex class have to be exposed as a REST service.

  • OAuth 2.0 JWT Bearer Token Flow: Allows you to authenticate salesforce via OAuth 2.0 JWT Bearer Token Flow.

  • OAuth 2.0 SAML Bearer Assertion Flow: Allows you to authenticate salesforce via OAuth 2.0 SAML Bearer Assertion Flow.

Version 6.2.0 Fixes

  • Created getServerURL operation to return the URL of the server.

  • Added support for Proxy configuration for all authentication types.

  • Added Fetch All Apex SOAP Metadata checkbox (The connector tries to perform Datasense for all Apex SOAP classes only if this checkbox is selected. )

  • NullPayloadToXMLStreamReader is hidden from the Studio as it is for internal use only.

  • SubscribeTopic operation now supports topic names without leading /'.

  • Added support for CSV batch uploads (when contentType is set to CSV). Renamed the invokeApexMethod operation to invokeApexSoapMethod.

Version 6.2.0 Known Issues

  • This version is not compatible with Salesforce API v28.0, v29.0 and v30.0.

  • It doesn’t support the following data types for Apex Rest:

    • Custom Types

    • Lists of Lists or Maps

    • Maps of Lists or Maps

    • Object (not able to perform DataSense on it)

    • Blob (not supported by Salesforce Rest methods as input/output)

Salesforce Connector 6.1.0 - March 31, 2015

Version 6.1.0 Compatibility Information

  • Mule Runtime: 3.5.2 and later

  • Anypoint Studio: October 2014

  • Salesforce: v32.0

Version 6.1.0 Features

  • Salesforce Apex API - the connector now supports the following Apex operation:

    • invokeApexMethod - invokes any operation from an Apex class that is exposed as SOAP web service.

  • Added Query Builder for querySingle and queryAll operations.

  • Added payload as default value for the Ids input for retrieve() and emptyRecycleBin() operations.

Version 6.1.0 Fixes

None.

Version 6.1.0 Known Issues

None.

Salesforce Connector 6.0.1 - February 25, 2015

Fixes an issue where the Salesforce 6.0.0 connector didn’t work with Java 6. The connector now works correctly with Java 6 and 7. Everything else is the same as Salesforce 6.0.0.

Salesforce Connector 6.0.0 - February 23, 2015

Version 6.0.0 Compatibility Information

  • Mule Runtime: 3.5.2 and later

  • Anypoint Studio: October 2014

  • Salesforce: v30.0 to v32.0

Version 6.0.0 Migrating From Older Versions

If you’re currently using an older version of the connector, a small popup appears in the bottom right corner of Anypoint Studio appears as Updates Available. Click that popup and check for available updates. Click the Salesforce Connector version 6.0.0 checkbox, click Next, and follow the instructions provided by the user interface. When prompted, restart Studio.

When creating a flow and using the Salesforce Connector, if you have several versions of the connector installed, you might be asked which version you would like to use. Choose the version you would like to use.

Version 6.0.0 Features

Salesforce Metadata API - the connector now supports the following Metadata operations:

  • createMedatada - Adds one or more new metadata components to your organization.

  • deleteMetadata - Deletes one or more metadata components from your organization given an object’s API names.

  • describeMetadata - Retrieves the metadata which describes your organization. This information includes Apex classes and triggers, custom objects, custom fields on standard objects, tab sets that define an app, and many other components.

  • deployMetadata - Use this call to take file representations of components and deploy them into an organization by creating, updating, or deleting the components they represent.

  • listMetadata - Retrieves property information about metadata components in your organization.

  • readMetadata - Returns one or more metadata components from your organization for one or more object’s API Names.

  • renameMetadata  - Renames a metadata component in your organization, given its old API name and the new name.

  • retrieveMetadata  - This call retrieves XML file representations of components in an organization.

  • updateMetadata - Updates one or more metadata components in your organization.

  • upsertMetadata - Creates or updates one or more metadata components in your organization.

Version 6.0.0 Fixes

  • Security token is not required when IP restrictions apply.

  • Made API version configurable for OAuth connections.

  • Added ability to set readTimeout and connectionTimeout.

  • Fixed: Issue regarding missing fields on EXO created through the connector.

  • This connector no longer throws NullPointerException when an object to retrieve by ID has been deleted in Salesforce.

  • The useDefaultRule option now is passed in a SOAP request message.

  • Exposed operation to get SessionID from Salesforce connector.

Version 6.0.0 Known Issue

This version is not backward compatible with Salesforce API versions v28.0 and v29.0.

Salesforce Connector 5.4.12 - March 11, 2015

  • Security token is not required when IP restrictions apply.

  • Made API version configurable for OAuth connections.

  • Added ability to set readTimeout and connectionTimeout.

  • Fixed: issue regarding missing fields on EXO created through the connector.

  • Fixed: SFDC connector throws NullPointerException when object to retrieve by Id has been deleted in Salesforce.

  • Fixed: useDefaultRule option not been passed in soap request message.

  • Exposed operation to get SessionID from Salesforce connector.

  • Support for the SAML "bearer assertion flow".

Version 5.4.12 Compatibility Information

  • Mule Runtime: 3.5.2 and later

  • Anypoint Studio: October 2014

  • Salesforce: v28.0 to v29.0

Version 5.4.12 Migration Information

If you currently use an older version of the connector (5.4.10 for example):

  1. In Anypoint Studio, click the Updates Available popup, which appears in the lower right corner of Studio.

  2. Click the Salesforce Connector Version 5.4.12 checkbox. 

  3. Click Next and then follow the instructions provided by the user interface. When prompted, restart Studio.

  4. After restarting, when creating a flow and using the Salesforce Connector, if you have several versions of the connector installed, you may be asked which version you would like to use. Choose the version you would like to use.

MuleSoft recommends that you install the latest version of Studio.

Salesforce Connector 5.4.10 - October 28, 2014

  • Fixed a critical bug related to URL population in the connector

  • Updated DevKit version support

  • Bug fix: Problem with retrieving metadata when a URL is not specified in a connector configuration.

  • Compatibility:

    • Mule Runtime and DevKit: 3.5.1

    • Anypoint Studio: October 2014

    • Salesforce SOAP, Bulk, and Streaming API: 3

Salesforce Connector 5.4.9 - September 18, 2014

Features:

  • Updated Salesforce SOAP, Bulk, and Streaming APIs to support version 31

  • Validated and documented support for SAML assertion flows using SFDC configuration

  • Tested and validated the Salesforce Connector for use with CloudHub

  • Added guidelines for connector version migration

  • Fixed issue related order-by in a query operation

  • Fixed bug related to importing a working cascade SFDC project

Salesforce Connector 5.4.7

  • Added Salesforce SOAP API headers support

  • Added new exception handling for REST and SOAP API

  • Removed Paginated Query operation (since AutoPaging for Query and QueryAll)

  • DevKit 3.5.0

Salesforce Connector 5.4.6

  • Added NonPaginatedQuery operation for backward compatibility since

  • Query uses Mule 3.5 AutoPaging

  • Added batchSize for queries

  • DevKit 3.5.0

Salesforce Connector 5.4.4

  • Fixed new Jetty dependencies for Mule 3.5.0

  • Fixes for authorizationUrl and accessTokenUrl in OAuth

  • DevKit 3.5.0

Salesforce Connector 5.4.3

  • Added compatibility with the new Mule Batch module

  • Added configurable for MAX_DEPTH for BULK API

  • DevKit 3.5.0

Salesforce Connector 5.4.2

  • Added getServerTimestamp operation

  • New exception handling for reconnection strategy

  • Fixed issues with proxies

Salesforce Connector 5.4.1

  • Added Mule 3.5 AutoPaging support for Query and QueryAll

  • Added DSQL support

  • Added operation to retrieve JobInfo

  • Added a way to allow empty security tokens

  • Fixed Date values for Nested SObjects in Bulk API

  • Fixed QueryResultStream issue when service return more than one page

  • DevKit 3.5.0

Salesforce Connector 5.4.0

  • Moved force-wsc as a dependency

  • Added support for API v28

  • Added support for recursive SObjects

  • Added sessionId and serviceUrl parameters on connection

  • Fixes for streaming API reconnection

  • Added support for reference types that differ from the field name

  • DevKit 3.5.0

Salesforce Connector 5.3.1

  • Upgraded DevKit to 3.4.0

  • Added support for streaming with OAuth

  • Fixes for streaming API

Salesforce Connector 5.3.0

  • Upgraded DevKit to 3.4.0

  • Added Mule 3.4 metadata support

Salesforce Connector 5.2.0

  • Upgraded to API v26

  • Added setPassword operation

  • Fixed documentation issues

Salesforce Connector 5.1.3

  • Upgraded to DevKit 3.3.2

  • Added paging capabilities with paginated-query method

  • Added support for Object Search queries using SOSL

  • Fixed SessionTimedOutException INVALID_SESSION_ID when doing

  • Fixed several concurrent requests with a timed out session

  • Fixed get-deleted and get-updated operations

  • Fixed blocking account when trying to disconnect if credentials are wrong

  • Updated documentation and fixed documentation issues

Salesforce Connector 5.1.2

  • Fixed issue related to ObjectStoreManager injection and get-updated-objects.

Salesforce Connector 5.1.1

  • Fixed issue related to URL transformer with DevKit 3.3.1.

See Also

  • Learn how to Install Anypoint Connectors using Anypoint Exchange.

  • Access MuleSoft’s Forum to pose questions and get help from Mule’s broad community of users.

  • To access MuleSoft’s expert support team, subscribe to Mule ESB Enterprise and log in to MuleSoft’s Customer Portal.