Salesforce

The Salesforce connector no longer works

Problem - While attempting to use flows connected to Salesforce, the user receives an error mentioning an expired token. This is due to expiring of Salesforce connector post 14 days of not accessing.

Solution - Refresh your Salesforce token. To navigate to the create a connector wizard, refer to Creating a Connector.

1.

In the Project Console, select on the Control Panel button.

2.

Select on the Connectors button.

3.

Select your Salesforce connector in the List view.

The Basic settings page displays for your Salesforce connector

4.

Select the Configure button.

The Edit connector environment window displays.

5.

For the Smart Flows buttons in Salesforce option, select Skip.

6.

Select the Next button.

7.

Select the Authorize Smart Flows button to connect to your Salesforce instance.

The application redirects you to Salesforce for authenticate. The Salesforce Allow Access window displays.

8.

If your credentials are valid, select the Allow button.

The Smart Flows is authorized displays under the Authorize Smart Flows button. This confirms that Smart Flows is now allowed to communicate with Salesforce.

9.

Select the Next button.

The Create connector Connected window displays.

10.

Select the Finish button.

The Salesforce connector is successfully created.

Unable to Run a Flow in Salesforce

Problem - After triggering flows in Salesforce, the Flow Execution Panel does not open. This issue is the result of a user having insufficient permissions in Salesforce.

Solution - The Smart Flows versions earlier than 4.18 must configure Salesforce users to have the following permissions set by their administrator in the user roles settings:

• View Setup and Configuration

• Assign Permission Sets

• Manage User

For more details on permissions, please refer to the PermissionSetAssignment.

Smart Flows versions 4.18 and later must have the following:

• Salesforce users with a role of ExperlogixSmart Flows User role or higher

• The profile for the Salesforce user must be set to "Minumum Access - Salesforce"