Articles in this section

See more

Getting Stuck at the first dot of connection in Salesforce

  • Updated
Follow

mceclip0.png

If you are unable to connect to SightCall in Salesforce and are getting stuck at the first dot of connection when attempting to connect to SightCall from Salesforce, then you can apply the following steps to resolve the issue:

  1. Go to Salesforce Setup (NOT Settings) > Static Resources > sightcall_console > click "View file"


    and make sure you see a code / script as a result: 
    window.SightcallConsole = function(params) {
  var url = null;
  var console2 = null;
  var isOpen = false;
  var isTryOpen = false;
  var callbacks = [];
  var timer;

  window.WIDTH_DEFAULT = 700;
  window.HEIGHT_DEFAULT = 600;

  this.isOpen = function() {
    return isOpen;
  };

...
    and not a 404 error:

    If you see 404 error, then the issue is outside the scope of Sightcall Support.  You will need to get Salesforce Support involved to disable permissions related to the following Salesforce Release updates:
    1. https://issues.salesforce.com/issue/a028c00000gAxCiAAK/enable-secure-static-resources-for-lightning-components-throws-error-accessing-a-static-resource-if-its-from-a-package-with-underscore-in-namespace
    2. https://issues.salesforce.com/issue/a028c00000gAw4uAAC/winter-21--enable-secure-static-resources-for-lightning-components-causes-a-cors-issue-for-static-resources-loaded-from-an-aura-component

  2. Login to admin.sightcall.com > click Integrations on left menu under the setup tab (this will open a new browser tab accessing services.sightcall.com) > click Salesforce tile > make sure your SFDC domain is correct and PIN Code & Use Webhooks = enabled (checked) > Hit Save and it will redirect you to SFDC.  Once you're in SFDC, click allow of any SFDC permissions request that pops up.
     mceclip4.png
    mceclip5.png

  3. Go to Salesforce Setup > Remote Site Settings > make sure "sightcall_prod" exist and is set to  either https://salesforce.sightcall.com (for EU Core tenants) or https://salesforce-us.sightcall.com (for US Core tenants).
    mceclip2.png

  4. Go to Salesforce Setup > Session Settings > set Lightning Web Security and Enable Stricter Content Security Policy = disabled (unchecked).
    mceclip1.png

  5. If none of the above steps works to fix the issue, then it's possible that the SightCall Salesforce package installation has not been fully completed.  Depending on how large your SFDC Org is, it can take up to 24 hours for SFDC to completely recompile the Apex Classes as a result of the SightCall Salesforce package installation. 

    If you need to manually recompile the Apex Classes, you can go to Salesforce Setup > Apex Classes > click Compile all classes and wait for a while.
    mceclip0.png

    Afterwards, please make sure that you CLEAR ALL BROWSER CACHE AND COOKIES related to your SFDC.

Related articles