cloud-solutions-banner

Remedyforce Consulting: Salesforce API endpoint retirement Jan. 1, 2016 – Action Required

By Kedar Zavar, Senior Consultant, Cloudaction


Salesforce has announced that the API endpoint https://www.salesforce.com will be retired Jan. 1, 2016. Because Remedyforce runs on the Salesforce platform, this means that Remedyforce integrations using https://www.salesforce.com as a step—including all Pentaho transformations—must be updated to Salesforce’s new official endpoint, https://login.salesforce.com, before the end of the year.

What will happen if you don’t update the Salesforce API endpoint

If you do not update to the Salesforce’s new endpoint, https://login.salesforce.com, by Jan. 1, 2016, your API integrations will not work and your API calls will result in a “404 (Page Not Found)” error screen.

How to update your API connections

Our mission at Cloudaction is to ensure that your Remedyforce environment is generating maximum value for your organization. So, we want to go the extra mile to make sure you have made the required Salesforce API updates and to extend our help to ensure that you experience no disruptions to your Remedyforce environment due to the Salesforce API. We also are offering a free one-hour technical session to help you through the API update process. To take advantage of this offer, just send us a request via our Ask Us NOW! web form.

Following is a list of proactive steps to make sure your Remedyforce integrations are aligned with Salesforce’s new API connection.

Pentaho Integrations

Remedyforce users rely on Pentaho for common integrations.

1 SF API

And because every Pentaho transformation uses a Salesforce connection, you will need to update every connection by replacing “www” with “login”.

What you need to do

1. Look for every KTR file with the “Salesforce Input” step (see icon below).

2 SF API

2. Open the connection to displace the Salesforce web service URL. For instance, your Salesforce web service URL is https://www.salesforce.com/services/Soap/u/32.0

3 SF API

3. Update the Salesforce web service URL to https://login.salesforce.com/services/Soap/u/32.0

4 SF API

Again, note that the only change is to replace “www” with “login” in the Salesforce web service URL.

4. Test the connection. Then go to File and select Save to save the change.

NOTE: BMC’s Virginia Leandro has posted a great Saleforce API retirement video on YouTube that also walks you through this process.

Checklist for common Pentaho integrations

Following is a brief summary of API changes required on common Pentaho integrations.

Remedyforce LDAP Pentaho Package with Permission Sets (latest OOTB package)

5 SF API

Remedyforce SCCM Integration CMDB 2.0

6 SF API

Remedyforce ADDM Integration

7 SF API

Remedyforce Configuration migration

Open required .KJB file > Menu > Edit > Settings > Parameters > validate SF_DESTINATION_ORG_APIURL and SF_SOURCE_ORG_APIURL

Remedyforce API integrations for other apps

Make sure you validate all integrations using custom code from Remedyforce to other apps, web service calls, etc.

8 SF API

References

In addition to Virginia’s YouTube video, here are a few good sources of information on Salesforce API endpoint retirement from Salesforce and BMC.

Closing Thoughts

This blog highlights common Remedyforce integrations affected by the Salesforce API endpoint retirement. Your organization may have other integrations, however. If you have any questions, please reach out to the Cloudaction team. We are here to help.

At Cloudaction, our goal is to help you get maximum value from your Remedyforce experience. We welcome your comments and suggestions. Please don’t hesitate to contact us at 1-844-2CLOUDA (1-844-225-6832) or via Ask Us NOW!, a complimentary service from Cloudaction to provide expert answers to your product capability, functionality, and implementation questions. We promise to respond to your inquiry or question within 24 hours.

Tagged with: ,
Posted in Remedyforce

Recent Posts