@fusebit/salesforce-connector v1.0.3

Fusebit Salesforce Connector

This is the Fusebit Salesforce Connector, a simple way to to implement a multi-tenant, bi-directional integration between your application and Salesforce, on top of the Fusebit platform.

Getting started

Assuming you are a subscriber of Fusebit, you would start by using the fuse CLI to deploy a Fusebit Salesforce Connector Manager to your subscription:

git clone git@github.com:fusebit/salesforce-connector.git
cd salesforce-connector
fuse function deploy --boundary managers salesforce-connector-manager -d ./fusebit

Soon enough you will be writing code for your integration logic. Get in touch at Fusebit for further instructions or to learn more.

Organization

• lib/connector contains the core Fusebit Salesforce Connector logic that manages authentication to Salesforce.
• lib/manager contains the Fusebit Salesforce Connector Manager logic which supports the install/uninstall/configure operations for the connector.
• lib/manager/template contains a template of a Fusebit Function that exposes the Fusebit Salesforce Connector interface. As a developer, you will be spending most of your time focusing on adding your integration logic to VendorSalesforceConnector.js.
• fusebit contains a template of a Fusebit Function that exposes the Fusebit Salesforce Connector Manager interface.

Running tests

Here are a few things you need to know before running tests:

• You must have access to a Fusebit subscription.
• You must have the Fusebit CLI installed.
• You must have a Fusebit CLI profile configured with an account ID and subscription ID, and sufficient permissions to manage all functions and all storage on that subscription.
• The test will create and remove functions in randomly named boundary in the subscription.
• The test will create and remove storage objects in randomly named storage ID in the subscription.

To run the tests, set the FUSE_PROFILE environment variable to the Fusebit CLI profile name to use:

FUSE_PROFILE={profile-name} npm test

In case of a failure, you can get useful, verbose diagnostic information with:

debug=1 FUSE_PROFILE={profile-name} npm test

Release notes

1.0.3

• Fix a bug that prevented access tokens from being refreshed due to Salesforce not providing the expires_in property in the OAuth token response.

1.0.2

• Updating oauth-connector to 1.3.1

1.0.1

• Bugfix for default implementation of "getOpportunities"

1.0.0

• Initial implementation.