This article is a placeholder to document how to install the SQL-Sales managed package (the App Exchange application is live and ongoing). The url of this page is embedded into the deployed package.
Until approved by the Salesforce App Exchange, the managed package can only be installed into a sandbox, using this installation url.
During this period, pre App Exchange, SQL-Sales can still be deployed and actively connected to a Production instance using OAuth2.0, via the "beta" checkbox on the Environment Configuration page - this bypass works exclusively via the custom connected app you setup yourself and is not dependent on the installed managed package.
Installing the Package
Choose "Install for Admins Only"
"View components"
The "SQLSalesUndeleteService" Apex Class (and associated Test Class) provides a custom REST api, supporting undelete functionality. This allows a full range of data operations via the OAuth 2.0 connection (as undelete is not supported by default by the Salesforce REST api, only the SOAP api supports this by default).
The "SQL Sales" Connect App handles the connection itself (from the installed SQL-Sales Daemon).
Click the acknowledgment below and Install
Installation in progress...
Installation Complete!
Ignore the "help.sql-sales.com refused to connect" if you experience this - if you click on "View on another browser", see below, you can see the installation instructions, it's trying to display.
Managed Package installation
Finally Click "Done"
Installed Packages
click onto "SQL-Sales"
View Components
Click "View Components" to see what you have installed
As previously described - the package consists of a Connected App and an Apex class.
SQL Sales Connected App Configuration
We need to make some post installation configuration changes. From Setup, type "app" and navigate to Apps >> App Manager.
You will have an entry for "SQL Sales" Connected (Managed).
Click "Manage"
Click "Edit Policies"
OAuth Policies
Step 1
By default your installed connected app will have Permitted Users set to: "All users may self-authorize"
Change Permitted Users to: "Admin approved users are pre-authorized"
Click OK on the confirmation prompt below:
Step 2
By default "Issue JSON Web token (JWT)-based access tokens is not enabled
Tick the checkbox and leave the default token timeout at 30 Minutes (SQL-Sales at run time will validate this setting is 30 minutes).
Click Save
Step 3
Back on the SQL Sales Connected App Detail page, click on "Manage Profiles"
Click "System Administrator"
For completeness and general awareness, you can tick the "SQL Sales" checkbox in the Connected App Access section of the System Administrator Profile page.
Either method, will result in the below, on the SQL Sales Connected App detail page:
Step 4
You must now follow the instructions here to setup your connection for the given Salesforce instance you wish to connect to (in our example here, the "Test2" sandbox)
Note, during this beta period, if you have installed the Managed Package (i.e. this article) you therefore do not need to click the "beta" checkbox below in the Environment Configuration window. That checkbox is to allow the use of OAuth 2.0 in a Production instance without the need of the managed package installation.
