remove instance names from URLs

  • 0
  • 1
  • Question
  • Updated 6 months ago
  • Answered
Hello: 

We have received a Critical Update Expected March 16, 2019 that will affect our RingCentral integration due to our Org Instance. 

Critical Update Name: Remove Instance Names From URLs for Visualforce, Community Builder, Site.com Studio and Content Files

Critical Update Language: 

Prior to Winter '18, Visualforce, Community Builder, Site.com Studio, and content file URLs included the instance name of the org, even when a My Domain name was deployed.

After this update, any URL that includes the instance name, such as a bookmark, will automatically redirect to the new hostname.

Test this Critical Update
To ensure that the new URLs work with firewalls and proxy servers in the network path between your users and Salesforce, we recommend that you test this update in a sandbox. Any firewalls and proxy servers that filter by hostname must additionally trust *.visualforce.com, *.documentforce.com, and *.salesforce-communities.com.

We’ll enable this critical update on the auto-activation date.

While I realize this is a Salesforce Setting, they were not able to tell us if we need to remove the instance name on the due date from the CTI Adapter URL located in the Call Centers "Cloud Phone App v2".  Does RingCentral or Salesforce automatically update this, or is the instance hard coded in the RingCentral application for each customer.

CTI Adapter URL: https://vcp--rcsfl.na59.visual.force.com/apex/OpenCTIIndex999 
Instance Name = na59
Photo of Syed Shah

Syed Shah

  • 70 Points
  • hopeful

Posted 6 months ago

  • 0
  • 1
Photo of Jitender Kumar

Jitender Kumar, Director Application Development

  • 1,678 Points 1k badge 2x thumb
Hello Syed, 
Thanks for writing to us. In our tests what we have noticed is that Salesforce is much more fault tolerant now. For example if you put CTI URL as https://rcsfl.na35.visual.force.com/apex/OpenCTIIndex and let's say your Salesforce is in POD59,  Salesforce now will automatically redirect to POD59 even if you have the incorrect URL. You will have to be careful however to make sure your URL is a valid Salesforce URL for example na35 here is valid Salesforce POD.