Salesforce Connector Release Notes - Mule 3

Fixed SAML connection issues. (W-10925355)

Upgraded library dependencies. (CONN-9639, SE-23872)

Updated the Jetty IO from org.eclipse.jetty:jetty-io:9.4.19.v20190610 to org.eclipse.jetty:jetty-io:9.4.39.v20210325 to fix security vulnerabilities. (SE-21942)

The connector reconnection mechanism for sources sometimes created the Bayeux client multiple times, which caused the connector to receive platform events twice. (SE-19315)

Updated Apache Log4J log4j:log4j:1.2.17 to org.apache.logging.log4j:log4j-core:2.8.2 to fix security vulnterabilities. (SE-20064)

Added support for API v51.0.

The resume from last replay ID functionality of the Replay Topic and Replay Streaming Channel operations did not work properly when the retention window for a specific ID expired. (SE-19209)

The Upsert metadata operation failed to update the picklist metadata. (CONN-4637)

Too many sessions were created to communicate with the Salesforce API. (SE-16335)

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.

Salesforce Connector threw warning messages related to the replayId when starting a mule application that did not contain replay sources. (SE-15575)

The access token was not refreshed correctly when using the OAuth2 connection. (SE-15288)

A Query operation failed with MALFORMED_QUERY when it was written using the DataSense Query Language. (SE-15509)

Upgraded the DevKit to version to 3.9.9 to avoid errors related to the Enterprise License. (SE-13409)

Create operations did not support Long values for the object fields. (CONN-5423)

The Read Metadata operation filtered null values from the Salesforce response. (CONN-1664)

The Update operation was unable to send a proper request to Salesforce if a CustomField of type Picklist contained the ValueSet or ValueSetDefinition nested objects. (CONN-1693)

Added new connection providers to match the behavior of the Salesforce API that provides a single connection with the same credentials.

Added keep-alive functionality to the connection providers, meaning that a connector can try to keep the session alive even if it is not used. This functionality can be enabled or disabled by users.

Using the Replay streaming channel causes frequent disconnects and reconnects.

The application using Replay streaming channel records 401 and 403 error codes after some time and stops receiving messages.

The connector now generates the base URL from the endpoint configured by the client so that no problems arise when using a URL redirection service.

There was an issue performing a queryAll operation that instead of using the queryAll HTTP request, the connector was sending a query HTTP request. Fixed by properly handling queryAll use cases.

Fixed parsing of the SOQL for comma separated values and added support for date functions in where clauses.

Fixed nonpaginated query containing: count()

query operation ignores the fetch size.

getJobInfo operation fails if the contentType of the created job is not XML.

Unable to reconnect to Salesforce Streaming API

Salesforce Connector is not parsing MEL expressions for the OAuth 2.0 Username Password configuration.

Fixed an issue regarding the GlobalValueSetTranslation metadata object not being properly mapped to the Salesforce structure.

Customer received no error or exception on 403::Organization total events daily limit exceeded.

Salesforce Connector invoked the REST Apex and ignored null values.

Salesforce Streaming flow when set to processingStrategy as Synchronous does not catch exception strategy.

Salesforce topic disconnected when proxy with CONNECT.

CVE Security Vunerabilities in jackson-databind-2.4.3.

SFDC Connector: Buffering capacity exceeded. In previous versions, low buffering capacity could cause the capacity to be exceeded when several events have been queued. Now, the buffering capacity has been increased.

Reply topic losing messages. In previous versions, when there’s a network failure for less than 40 seconds (the amount of time needed to pass so that a resubscription to the topic triggers) and there are events that are sent for the pending HTTP request, those events are lost. Currently a resubscription is triggered when the connection is lost.

Added support for Salesforce API v40.0.

Support for publishing platform event messages using the Publish platform event message operation.

Added new metadata types

Provided new operations for Convert lead, Find duplicates by ids, Change own password

Apex SOAP call did not work when reconnection was triggered. In previous versions when the session was invalidated, the connector threw an error with this message Failed to invoke invokeApexSoapMethod caused by the org.apache.cxf.binding.soap.SoapFault No operation specified in request (the Body element has no child elements) exception. With this fix, the payload is retained and the calls work correctly after the reconnection.

There was a leak when the Salesforce Connector performed a reconnection. In previous versions when the Salesforce Connector performed a reconnection, HttpClient objects were leaking. With this fix, there are no leaks when reconnecting.

No error received by clients when the Organization total events daily limit was exceeded. In the previous version when there was an error of type 403::Organization, the total events daily limit exceeded the connector and did not throw an error or exception. In current version besides throwing an exception a notification is fired. The notification ID for this error is always be 100888 and it also contains the appropriate message.

Failure to refresh metadata

Salesforce topic subscription failure with API v37 v38 and v39

Added support for Salesforce API v39.0

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

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.

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.

Salesforce API

Metadata API

Added Generic Streaming support

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

Salesforce API

Metadata API

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.

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.

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

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.

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.

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

get-session-id

describe-global and describe-sobject

invoke-apex-rest-method

invoke-apex-soap-method

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

reset-password

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

Added support for List<String> for fieldsToNull.

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.

This version of the connector breaks backward compatibility:

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.

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.

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

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:

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

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

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.

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.

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:

Mule 3.5 and later

Anypoint Studio October 2014

Salesforce v32.0

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

Added Query Builder for querySingle and queryAll operations.

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

Mule 3.5 and later

Anypoint Studio October 2014

Salesforce v30.0 to v32.0

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.

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.

Mule 3.5 and later

Anypoint Studio October 2014

Salesforce v28.0 to v29.0