Installing / uninstalling the IntelligenceBank Connector for Salesforce Sales Cloud

Installing / Uninstalling The Connector

Download the latest Connector files from here.

For install, use the file: ib_connector_{{versionNumber}}

For uninstall use file: uninstall_ib_connector.zip

IMPORTANT: Before uninstalling the Connector, remove the “IntelligenceBank” component from all the pages where it was placed.

• Go to Workbench at https://workbench.developerforce.com/login.php

• Login to your Salesforce account and provide access to your organisation.
• Navigate to Migration -> Deploy

• Choose the file and complete all fields as follows:
  • Check Only: true (to run an initial validation of the installation process - DO NOT SKIP THIS STEP)
    
  • Rollback On Error: true
  • Test Level: RunSpecifiedTests
  • Run Tests: ib_IntelligenceBankDownloadPageCtrlTest,ib_DatabaseUtilsTest,ib_ConnectorActionsPicklistTest
    

• Click “Next”. You will be redirected to this screen:

• Click “Deploy” and wait till it will be finished.

• If the result is success: true, repeat the same steps, but with Check Only: false this time.

The Connector should now be installed, and a new Permission Set should have automatically been created. 

To enable the Connector on different Pages, see this article.

Error Handling

In case of error in the previous steps, copy the first 15 of 18 characters of the deployment Id value.

Open your Salesforce organisation and from Setup, navigate to the “Deployment Status” page.

Find the deployment job with the copied deployment Id values. After clicking on “View Details”, you should be able to see the “Component Errors” section at the bottom of the page.

If an error occurred during uninstallation and errors similar as on the screenshot above appear, it means that the IntelligenceBank component was not removed from all the Pages.

If you have any other errors please contact us here

Release Notes

Version 1.5

• Added allow="clipboard-write" to fix copying Public Links to clipboard on Chrome following security change
• Updated metadata API version to 60.0
• Reduced amount of page reloads by adding ResfreshAPI
• Fixed spinner in cmp