Nav

Salesforce Composite Connector Release Notes

The Anypoint™ Connector for Salesforce Composite provides you a way to integrate with Salesforce Composite API Salesforce Composite API. The connector exposes convenient methods for preparing sub-requests, execute them in one batch and parse the results. It provides DataSense on both preparation of sub-requests and parsing response of their execution.

Version 1.0.1 - September 5, 2017

Version 1.0.1 Compatibility

The Salesforce Composite 1.0.1 connector is compatible with:

Application/Service Version

Mule Runtime

3.7.5 or later

Salesforce Rest API

v36.0

Version 1.0.1 Features

  • Addition of Proxy Support: Starting with version 1.0.1 the Salesforce Composite Connector allows the connection using a PROXY.

Version 1.0.1 Fixes

  • INVALID_SESSION_ID not triggering reconnection strategy: Previously, when the Invalid Session Id exception occurred the reconnection strategy did not kick in as expected. Now, when such an exception occurs the reconnection strategy is successfully started.

  • Propagate errors from Salesforce Composite connector: In previous versions, the exception handling for the Salesforce specific errors was hidden by the connector and no details about the error encountered was visible to the user. Now, error details such as status code and exception message are forwarded to the end user.

Version 1.0.1 Known Issues

  • Support for TLS1.0 is discontinued in Salesforce.

  • If by default the application tries to use TLS1.0, then, when running it, the following VM argument should be added: -Dhttp.protocols=TLSv1.1,TLSv1.2 This will ensure the fact that TLS1.1 or TLS1.2 will be used for the communication with Salesforce.

Version 1.0.0 - March 10, 2016

Release Notes for version 1.0.0 of the Salesforce Composite connector. These Release Notes accompany the Salesforce Composite Connector User Guide.

Version 1.0.0 Compatibility

The Salesforce Composite connector is compatible with:

Application/Service Version

Mule Runtime

3.5.0 and higher

Salesforce Rest API

v36.0

Features

  1. Prepare sub-request for "Create" new SObject.

    • The purpose of this method is to provide metadata for create operation based on the object that is going to be created and generates the sub-request.

  2. Prepare sub-request for "Update" existing SObject.

    • The purpose of this method is to provide metadata for update operation based on the object that is going to be updated and generates the sub-request.

  3. Prepare sub-request for "Delete" existing SObject.

    • The purpose of this method is to provide metadata for delete operation based on object that is going to be deleted and generates the sub-request.

  4. Prepare sub-request for "Retrieve" existing SObject.

    • The purpose of this method is to provide metadata for delete operation based on object that is going to be deleted and generates the sub-request.

  5. Prepare sub-request for "GetLimits".

    • The purpose of this method is to provide metadata for getLimits operation and generates the sub-request.

  6. Prepare sub-request for "Query" existing SObjects.

    • The purpose of this method is to provide metadata for query operation based on the object that is going to be queried and generates the sub-request.

  7. Prepare sub-request for "QueryAll" existing SObjects.

    • The purpose of this method is to provide metadata for query operation based on object that is going to be queried and generates the sub-request.

  8. Prepare sub-request for "Search" into existing SObjects.

    • The purpose of this method is to provide the user a way to input a SOSL String and generates the sub-request.

  9. Execute a list of sub-requests in one API call.

    • The purpose of this method is to send all the sub-requests in one batch for execution to server.

  10. Parse sub-request result for "Create".

    • The purpose of this method is to provide metadata for the result of the create operation.

  11. Parse sub-request result for "Update".

    • The purpose of this method is to provide metadata for the result of the update operation.

  12. Parse sub-request result for "Delete".

    • The purpose of this method is to provide metadata for the result of the delete operation.

  13. Parse sub-request result for "Retrieve".

    • The purpose of this method is to provide metadata for the result of the retrieve operation.

  14. Parse sub-request result for "GetLimits".

    • The purpose of this method is to provide metadata for the result of the getLimits operation.

  15. Parse sub-request result for "Query".

    • The purpose of this method is to provide metadata for the result of the query operation.

  16. Parse sub-request result for "QueryAll".

    • The purpose of this method is to provide metadata for the result of the queryAll operation.

  17. Parse sub-request result for "Search".

    • The purpose of this method is to provide metadata for the result of the search operation.

  18. Create SObject Trees

    • The purpose of this method is to send a list of SObject trees to Salesforce to be created.

Version 1.0.0 Fixed in this Release

None.

Version 1.0.0 Known Issues

  • Support for TLS1.0 is discontinued in Salesforce.

  • If by default the application tries to use TLS1.0, then, when running it, the following VM argument should be added: -Dhttp.protocols=TLSv1.1,TLSv1.2 This will ensure the fact that TLS1.1 or TLS1.2 will be used for the communication with Salesforce.