SalesForce new endpoint with the Summer ‘17 release
-
Received an email about “SF new endpoint with the Summer ‘17 release” and wondering if the plugin will still work this summer. Here is the email from SF –
* Currently targeted for June 2017; date subject to change.
What is the impact of this change on customer orgs?
Websites using the W2C/W2L forms will cease to create new cases and/or leads within customers’ Salesforce orgs if the websites are not updated with the new endpoint URL by the Summer ‘17 release.NOTE: The W2C/W2L HTML code generator functionality will be updated to reference the new endpoint URL with the Summer ‘17 release. As such, W2C/W2L form HTML code generated from the Summer ‘17 or later HTML code generator will already include the new endpoint and websites using this HTML code will not be impacted by this change.
What action do I need to take?
Customers using either or both of these functionalities will need to update the W2C/W2L HTML code in their websites by the Summer ‘17 release. As the new endpoint URL is already available, customers are strongly encouraged to complete these updates as soon as possible to take advantage of the improved functionality performance. See the Updating the Web-to-Case and Web-to-Lead Endpoint URL article for more details.
-
We too got notification of this needing to be updated for a client. I did find that the plugin exposes a filter that allows you to make this update yourself if you have access and are comfortable editing to your theme’s files. Should work while waiting for a proper update.
Drop this in your active theme’s
functions.php/** *---------------------------------------------------------------------- * Updating the Web-to-Case and Web-to-Lead Endpoint URL *---------------------------------------------------------------------- * * See: https://help.salesforce.com/articleView?eid=ss-tc&id=Updating-the-Web-to-Case-and-Web-to-Lead-Endpoint-URL&language=en_US&type=1 * * Websites using the W2C/W2L forms will cease to create new cases * and/or leads within customers’ Salesforce orgs if the websites are * not updated with the new endpoint URL by the Summer ‘17 release. * */ function update_gf_salesforce_request_subdomain( $sub, $test ) { return $test ? $sub : 'webto'; } add_filter( 'gf_salesforce_request_subdomain', 'update_gf_salesforce_request_subdomain', 10, 2 );Current filter location in the plugin source:
gravity-forms-salesforce/inc/web-to-lead.php [line 711]Thank you, @curtisl! Your instruction was thorough and super helpful.
I echo @webvixn’s request of a way to double check to see if this is working other than by sending a lead and seeing it go through to SalesForce. If anyone knows of a way to double check, please let me know. The people I work with are still wary that we’ll be set for June.
Question @abdiyohan: why add this to functions.php instead of just editing the file directly? This plugin has not been updated in over two years and one would assume any updates at this point would include this change in SF functionality. Seems as though this modification would save a little by not adding additional lines/calls to functions.php
For those asking about how to test the updated code/endpoint that @curtisl graciously provided, if you enable the Gravity Forms Logging Plugin, it allows you to see the updated endpoint. Once you have the logging enabled, submit the form, and view the log. You should see something like the following:
2017-05-24 12:53:19.333695 - DEBUG --> This is the data sent to Salesforce (at https://webto.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8:Instructions here on how to enable the plugin and view logs.
- The topic ‘SalesForce new endpoint with the Summer ‘17 release’ is closed to new replies.
