Planning for Salesforce (Legacy) Integration

For version-specific support information, please see the Compatibility Matrix.
This content applies to legacy components (such as K2 Studio and K2 for Visual Studio), legacy assemblies, legacy services or legacy functionality. If you have upgraded from K2 blackpearl 4.7 to K2 Five, these items may still be available in your environment. These legacy items may not be available in new installations of K2 Five. These legacy items may also not be available, supported, or behave as described, in future updates or versions of K2. Please see the legacy component support policy for more information about support for these components.

K2 integrates with Salesforce.com through the Salesforce Service Broker. One can register an instance of this broker that points to a Salesforce account, which exposes entities within that company as Service Objects that are referenced by SmartObjects. These SmartObjects can in turn be consumed by SmartForms, workflows, reports and other SmartObject consumers.

Salesforce is disabling the TSL 1.0 encryption protocol across their services in July of 2017. At that time all inbound or outbound connections to Salesforce must use TLS 1.1 or TLS 1.2 encryption protocol. For more information on the Salesforce changes, see the following two articles:

Also see the K2 article KB001764 for information.

Until July 2017 you can disable this TLS 1.1 requirement in your Salesforce account, reverting to TLS 1.0 and your K2 integration with Salesforce will continue to work.

The Broker Management tool, Salesforce security provider, Salesforce SmartObject Service Instance and Salesforce SmartObject Instance Generator has been updated to .NET 4 to support TLS 1.1/TLS 1.2.

For information on preparing for Salesforce integration, see the Configure Salesforce Integration topic. For information on using the service broker, please see the Salesforce Service Broker topic in the user guide.

There are no specific installation steps required to install this Service Broker, it is included and available by default in a K2 environment.