Will this impact Saltbox integrations?

Yes. The Saltbox Salesforce Connector configuration will need to be updated with a newly generated user security token.

The connector itself will not be impacted by this change because it does not use hardcoded URLs nor rely on Salesforce Express Connect services (both of which are impacted by this migration).

What should Saltbox customers do? 

1. Saltbox Customers will need to regenerate their user security token by following the instructions outlined here: User Security Token Regeneration Guide. We will provide documentation for the above setting change in Saltbox.
   
   
2. Postpone Your Migration to HyperForce. HyperForce is a new environment. Although we don't anticipate any issues with Saltbox integrations, Vision33 plans to perform rigorous testing to ensure Saltbox customers do not experience any disruption from the migration of their Salesforce instances.  For this reason, we suggest that customers delay their migration until we have had an opportunity to complete our testing. We anticipate having access to the Hyperforce environment sometime after October 18. Salesforce documentation indicates that customers can reschedule their migration to a later date if needed.

Helpful links

• General information about Hyperforce: https://help.salesforce.com/s/articleView?id=000388902&type=1
• Salesforce pre-migration recommendations: https://help.salesforce.com/s/articleView?id=000392992&type=1
• How to reset your security token: https://help.salesforce.com/s/articleView?id=sf.user_security_token.htm&type=5