We are happy to announce the June ’15 release of the Salesforce Connector v6.2.1. With this release, we now support 56 different operations across multiple Salesforce APIs including the Apex REST API. This release also includes significant authentication capabilities such as OAuth v2.0 JWT bearer token and OAuth v2.0 SAML bearer assertion.
Benefits of using the Salesforce Connector
MuleSoft’s Salesforce Connector, as with any Anypoint Connector, provides a layer of abstraction that hides the complexity of the underlying APIs. By using this connector, you can perform operations such as Create, Read, Update, and Delete (CRUD) among many other operations as supported by the underlying APIs without having to sift through pages of API documentation. Moreover, MuleSoft’s DataSense technology enables you to create queries efficiently by retrieving metadata from your Salesforce instance through a user-friendly interface.
When you combine these features of the Salesforce Connector with examples and pre-built templates that integrate Salesforce with other popular SaaS and backend systems, you now have a powerful solution for Salesforce integration in Anypoint Platform.
Previously, the connector supported Basic Authentication and OAuth. With this new release, we are staying true to our commitment of providing enhanced security capabilities when connecting to Salesforce within Anypoint Platform. We now support JWT bearer token and SAML bearer assertion authentication flows as part of the connector configuration. You can access these capabilities from the Connector Configuration field as shown in the following screenshot.
- Consumer key: Consumer key of the connected Salesforce app obtained from salesforce.com
- Key store: Name of the .jks file stored under src/main/resources folder
- Store password: Password used to generate the keystore file
- Principal: Your Salesforce account username
- Ability to invoke APEX methods – APEX SOAP & APEX REST APIs
Expose your APEX methods so that external applications can access your code using the Salesforce connector. You can use the “Invoke SOAP Method”(v6.1.0) or the “Invoke REST Method”(v6.2.0) operation depending on whether you want to expose the APEX code using SOAP or REST protocols.
As you may already know, Apex is used to execute flow and transaction control statements on the Force.com platform server. Using the Invoke operations in the connector, you can now build custom responses or expose custom functionality from your Apex code efficiently within Anypoint Platform.
- Ability to manage customizations – Metadata API
Retrieve, deploy, create, update, or delete customization for your organization using the 10 metadata operations supported by the connector. The Metadata API is intended for managing customizations and for building tools that can manage the metadata model, not the data itself.
This is a great feature to use when you want to migrate changes from a sandbox or testing organization to a production environment. It eliminates the process of manually recreating the data structure in a separate Salesforce instance.
Apart from the aforementioned APIs, we provide extensive support for the Salesforce SOAP API and Bulk API based on the REST protocol. Over 37 different operations in the connector are covered by these two APIs alone, allowing you to perform crucial CRUD tasks in your Salesforce instance. The connector also supports the Streaming API through the Publish and the Subscribe topic operations, so that you can get near real-time notifications and reduce API calls.
Stay tuned for more updates. If you have any questions, please leave us a comment. Until next time – Goodbye! Ciao! Alvida! Adios! Au Revoir!
References and Resources
Release notes: Keep track of new features included with each version release