Integration between the In Mind Cloud Digital Sales Platform (DSP) and Salesforce (SFDC) is done through MuleSoft's Anypoint Platform™, where bulk transfer of Account and Contact information is supported. In order to complete this, properties need to be prepared to deploy the connector.

 

Preparing properties required from DSP

Step 1: Within DSP, first create a new Connected Client (Administration -> Connected Clients)

• Create a unique Name to be used as the Client ID.
• A Secret Key may be generated for use in the connection.
• For "Access Validity", enter high numbers to aid smooth connection.

Step 2: Create an employee and provision a user as needed for this client.

See 'Employee Management' and 'User Management' articles in the Admin Guide for more details.

 

With the above 2 steps, prepare the following properties: 

mx_protocol=HTTPS
mx_host=(URL example: mxpm01rq2oqfsbxr.hana.ondemand.com)
mx_basepath=iss(leave blank if not used)
mx_port=443

mx_username=(username)
mx_password=(default or reset password)
mx_client_id=(see Step 1)
mx_client_secret=(see Step 1)

Tip: To avoid running into too many errors while deploying, do first test your DSP URL and Password via Postman 

 

Preparing properties required from SFDC

To connect to Salesforce, the following properties are needed: 

sfdc.consumerKey=
sfdc.consumerSecret=
sfdc.username=(username)
sfdc.password=(passwordfollowedbysecuritytoken)
sfdc.tokenEndpoint=(URL example: https://login.salesforce.com/services/oauth2/token) 

These can be obtained through the following steps below:

• Create a Connected App in SFDC
• Manage your Connected App
• Generate an Initial Access Token
• Get SFDC Consumer Key and Consumer Secret key
• Get SFDC user Security Token

 

Create a Connected App in SFDC

To create a connected Salesforce app, follow these steps:

• Log in to Salesforce with your developer account
• In the drop-down list of the account (in the upper-right corner), select Setup
• In the left-hand pane, search for App Manager and open it
• Click on “New Connected App”

 

• On the New Connected App page, fill the following required fields under Basic Information:
  • Connected App Name. For example, "test". The connected app name must be unique within your org. If the connected app was created in the Spring ‘14 release or later, you can reuse the name of a deleted connected app. Only letters, numbers, and underscores are allowed, also avoid using names which ends with "builder".
  • API name. For example, "test".
  • Contact Email. your email.

 

• Go to API (Enable OAuth Settings) and select Enable OAuth Settings.
  • In the Callback URL field, enter https://login.salesforce.com/services/oauth2/token for a production Org and https://test.salesforce.com/services/oauth2/token for a Sandbox Org.
    If you have a custom domain enabled on your org, you must use the custom URL https://yourcustomdomain.my.salesforce.com/services/oauth2/token
  • In the Selected OAuth Scopes field, select Access and manage your data (api), and then click Add.
  • Click the Save button to save the new Connected App.

 

Manage your Connected App

• On the new app that you just created, click Manage

 

• On the page that opens, click the Edit Policies button.
  • Set IP Relaxation to: Relax IP Restrictions
  • Set Permitted Users to: All users may self-authorize

 

Generate an Initial Access Token

• Go back to the Connected Apps list, find the app that you just created then click on the "view" button on the right.
  • Scroll to the section Initial Access Token for Dynamic Client Registration, and click the Generate button to generate an initial access token. Salesforce requires this token to authenticate the client app's request at the dynamic client registration endpoint.

 

Get SFDC Consumer Key and Consumer Secret key

• Go to the API (Enable OAuth Settings) section, and note down the Consumer Key and Consumer Secret.

 

Get SFDC user Security Token

• Log in to Salesforce with your developer account
• In the profile avatar in the upper-right corner, select Settings
• In the left-hand pane, search for: Reset My Security Token and open it
• Click on “Reset Security Token”

 

Set up Email Notifications

Include the following for email notifications: 

email_subject = Mulesoft SFDC-DSP Connector
email_content = Mulesoft SFDC-DSP Flow Triggered. Please check.
email_error = Mulesoft SFDC-DSP Flow Failed. Please try again.

 

email_contactbulk_subject = Mulesoft SFDC-DSP Connector
email_contactbulk_error_content = Mulesoft SFDC-DSP Flow Contact Triggered. Contact Bulk sync has been completed, but some contacts failed to sync.
email_contactbulk_success_content = Mulesoft SFDC-DSP Flow Contact Triggered. Contact Bulk sync has been completed successfully.

 

email_contactbulk_content = Mulesoft SFDC-DSP Flow Contact Triggered. Contact Bulk sync has been completed successfully.
notification_receipts=(enter comma-separated emails as preferred)

 

Additional Properties to Run Automated Syncs

Even without manually triggering the connector sync, the account will sync based on this input (measured in minutes):

sfdc.frequency.account.upsert=15
sfdc.frequency.account.delete=15

sfdc.frequency.contact.upsert=15
sfdc.frequency.contact.delete=15

 

Note: The above screenshots and steps are updated as of 21/08 Release. Please refer to Mulesoft documentation for additional guidance: https://help.mulesoft.com/s/