Robert,
I think you might be confusing this with PureConnect. Your responses regarding "structured parameters" and "handlers" point to PureConnect rather than PureCloud.
When I look though the PureCloud Salesforce Integration configuration, the only thing I see that might drive what Salesforce Org is addressed by the Integration is the Integration Credentials configuration, the username and security token. I understand that if the username and security token stay the same, and Salesforce essentially moves to a different server cluster (or Org), more of a backend move, the PureCloud Salesforce Integration account will stay intact.
Richard Schott, am I correct?​
------------------------------
Greg Beal
ConvergeOne, Inc.
------------------------------
Original Message:
Sent: 03-26-2020 20:24
From: Robert Wakefield-Carl
Subject: Salesforce org migration
It depends. If it was me, I would have put the instance information into a structured parameter that could be changed at any point. I would also have put in the capability to use UAT or PROD based on a phone number in a parameter. I am guessing they did non of this originally and hard coded the instance URL into the handlers and call flows. If they are charging to change them now, make sure they make it easier next time. If you want some secondary quotes or help, we would be glad to talk to you.
Robert
------------------------------
Robert Wakefield-Carl
Avtex Solutions, LLC
Contact Center Innovation Architect
robertwc@avtex.com
https://www.Avtex.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 03-26-2020 07:26
From: Goodell Curtis
Subject: Salesforce org migration
In the next month or so, our Salesforce instance will be undergoing a Salesforce Org Migration. It will be moved from one instance to another during this time. When we reached out to Genesys they said that we would need to build new integrations and update all of our call flows. Why would we need to do this when the integration is pointed to login.salesforce.com, which isn't changing?
#Integrations