1.1 Install and Configure the Overcast App 

Installing Overcast

  1. Go to the AppExchange and select Get it Now  from the Overcast AppExchange Listing. Select Install for Admins Only and Install.



 

  1. You will receive a prompt to Approve Third-Party Access. These security settings give permissions to the Overcast App installed on your Salesforce org to contact the Overcast Server endpoints that are required for communication to and from the backend. Once you select Yes, grant access to these third-party web sites, you can then select Continue. 


 

  1. In the Setup Quick Find, search for Installed Packages. Confirm the Overcast Package has been installed.


 


Overcast Settings

  1. Navigate to the App Launcher and select Overcast. 

 
 

  1. Select the Settings tab, and choose your Overcast Endpoint (i.e the overcast server in you region). If this is for trial use in a Sandbox, please select the endpoint that properly reflects both your region and contains the sandbox denotation (i.e. "US1 (Sandbox)"). If the endpoint is custom, provide the URL for the endpoint. Once saved, the endpoint should not be changed. Changing the endpoint after it has been established can lead to malfunctions with Integration Scenarios.


 

  1. Under Error Notification, populate the email address that should receive any error messages from the Overcast package. This is optional, but recommended.



 

  1. Select Save at the top of the page. You should see a confirmation message.

 

Permission Sets

 

Overcast has provided permission sets that are required for users to have access to parts of Overcast, including components.  

  1. Overcast Design-time User
    Users who will create and maintain Overcast integration scenarios and configuration. It is expected that these users are already Salesforce administrators because Overcast operations require admin permissions, like deploying Apex code.
  2. Overcast Run-time User
    Users who will use Overcast integrations. This includes users who open record pages with Overcast Lightning Components, custom Lightning Components that call an integration scenario, or custom applications/pages that call integration scenarios.
  3. Each data synchronization scenario
    When a data synchronization scenario is activated, integration objects (custom objects that mirror the backend system API) are deployed with an accompanying permission set. Apply this permission set to any user that will be interacting with the integration objects. This interaction would typically be through a custom application or a trigger event that creates records to run a scenario.

 For more information on Permission Sets, click here.