Salesforce

Overview

⚠️ Note that the following sections are relevant only for the latest versions of the Salesforce Adapter (5.0 and later). For details on the legacy versions (3.0 and 4.0), see the Legacy Adapter section.

After installing the Salesforce Adapter in your organization, you can start interop-enabling your Lightning Web Components. If you intend on using Salesforce within the io.Connect Platform (io.Connect Desktop or io.Connect Browser), it's recommended to use the InteropConnectedComponentStandalone component that is distributed with the Salesforce Adapter package, as it provides the best possible interoperability performance for this case. This component can be used both in your Lightning Our apps, or from within the Salesforce platform (with certain limitations).

⚠️ Note that using Salesforce within the io.Connect Platform has the advantage of not having to attach an io.Connect Utility Bar component to your Lightning App and not having to provide additional package configuration after installation in order to enable interoperability. These steps, however, are required when using Salesforce in a web browser.

⚠️ Note that using the InteropConnectedComponentStandalone component to achieve interoperability between Salesforce and io.Connect Browser projects is still an experimental feature. This means that enabling some of the io.Connect Browser functionalities may require additional development.

Requirements

To use Salesforce within the io.Connect platform, you must provide a valid app definition for Salesforce, enable auto injection of the @interopio/desktop library, and provide the configuration necessary for using preload scripts. For instructions on how to create an app definition for io.Connect Desktop and io.Connect Browser projects, see the Salesforce App Definition section.

To be able to use the InteropConnectedComponentStandalone component, Lightning Web Security must be enabled:

Log in to your Salesforce organization as an administrator.
Go to Setup > Security > Session Settings.
Make sure that Lightning Web Security is enabled in the "Lightning Web Security" section.

Limitations

There are certain limitations if the InteropConnectedComponentStandalone is used from inside the Salesforce platform:

Due to the security restrictions imposed by Salesforce, it's impossible to achieve interoperability between interop-enabled LWCs in Salesforce and io.Connect Browser. To avoid this limitation, it's recommended to use the InteropConnectedComponentStandalone component in Lightning Out apps or Visualforce pages instead.
If using more than one instance of the component, all interop-enabled LWCs will have the same application name. This means that you won't be able to register more than one event listener for the same type of event. To avoid this limitation, it's recommended to use the InteropConnectedComponentStandalone component in Lightning Out apps instead.

Examples

Full working examples demonstrating interoperability between Salesforce and interop-enabled apps are provided via the interop.io Salesforce Adapter [demos] Salesforce package.

To retrieve the package into your project, execute the following command using the Salesforce CLI:

sf project retrieve start --package-name "interop.io Salesforce Adapter [demos]"

Salesforce App Definition

To be able to use Salesforce within the io.Connect platform, you must provide a valid app definition for it. The following sections describe how to create an app definition for Salesforce depending on whether it's running in io.Connect Desktop or in io.Connect Browser.

io.Connect Desktop

To be able to open Salesforce in io.Connect Windows or Workspaces in io.Connect Desktop, you must provide a valid app definition for it. Besides the standard required definition properties ("name", "type", and "url"), the other requirements are to enable auto injection of the @interopio/desktop library and configure the usage of preload scripts. Enabling auto injection is required because the @interopio/desktop library provides the interoperability capabilities of the InteropConnectedComponentStandalone component. The preload scripts configuration is required because it enables using the InteropConnectedComponentStandalone component.

⚠️ Note that the preload scripts configuration also allows you to enable the usage of a Utility Bar component. Using a Utility Bar component isn't necessary when Salesforce is running in io.Connect Desktop, but if you decide to use one, you must provide the respective preload script. For details on how to attach one of the available io.Connect Utility Bar components, see the Usage > Web Browser > Configuration section.

The following is an example configuration for defining Salesforce as an io.Connect app:

{
    "name": "salesforce",
    "type": "window",
    "title": "Salesforce",
    "details": {
        // URL pointing to your Salesforce organization.
        "url": "https://your-salesforce-url.salesforce.com/",
        // This is required to enable usage of preload scripts.
        "security": {
            "webSecurity": false,
            "allowRunningInsecureContent": true,
            "allowedExternalURISchemes": ["data", "https", "http"]
        },
        // This is required to enable interoperability and library usage in production.
        "preloadScripts": {
            "scripts": [
                // This preload script is required to enable using the `InteropConnectedComponentStandalone` component.
                "https://enterprise-demos.dev.interop.io/preload-scripts/salesforce-request-factory-from-platform.js",
                // This preload script is only necessary if you want to use a Utility Bar component when Salesforce is running in io.Connect Desktop.
                "https://enterprise-demos.dev.interop.io/preload-scripts/salesforce-utility-bar.js"
            ],
            "useBase64PreloadScripts": false
        },
        // Enable auto injection of the `@interopio/desktop` library.
        "autoInjectAPI": {
            "enabled": true,
            // If set to `false` (default), will enable you to provide initialization settings from your component.
            // If `true`, the library will be auto initialized with the default settings (e.g., you won't be able
            // to use features that are disabled by default such as the Workspaces API and the Search API).
            "autoInit": false
        }
    },
    "customProperties": {
        // Use this if you want to add Salesforce to the "Add App" menu in a Workspace.
        // This will enable users to open Salesforce in Workspaces.
        "includeInWorkspaces": true
    }
}

io.Connect Browser

To be able to open Salesforce in io.Connect Windows or Workspaces in io.Connect Desktop, you must provide a valid app definition for it when initializing your Main app.

The following is an example configuration for defining Salesforce as an io.Connect app:

import IOBrowserPlatform from "@interopio/browser-platform";

const config = {
    licenseKey: "my-license-key",
    applications: {
        local: [
            {
                name: "salesforce",
                type: "window",
                title: "Salesforce",
                details: {
                    // URL pointing to your Lightning Out app in your Salesforce organization.
                    url: "https://your-salesforce-url.salesforce.com/"
                },
                customProperties: {
                    // Use this if you want to add Salesforce to the "Add App" menu in a Workspace.
                    // This will enable users to open Salesforce in Workspaces.
                    includeInWorkspaces: true
                }
            }
        ]
    }
};

const { io } = await IOBrowserPlatform(config);

Usage

The following sections describe the InteropConnectedComponentStandalone component API and provide examples on how to implement an interop-enabled LWC.

Component API

The InteropConnectedComponentStandalone component provides a set of properties and methods that you can use to interop-enable your LWC.

The component has the following properties that can be used in its HTML file:

Property	Type	Description
`application-name`	`string`	Name for the component that will be used by the io.Connect framework when interacting with other interop-enabled apps.
`factory-config`	`object`	`Config` object passed to the `IODesktop()` factory function for initializing the `@interopio/desktop` library or a `Config` object passed to the `IOBrowser()` factory function for initializing the `@interopio/browser` library depending on the io.Connect platform your are using. Defaults to `{}`.
`connected-methods`	`object`	Key/value pairs of Interop method names and the names of the DOM events that they will handle (e.g., `{ "My.Method": "my_event" }`). If you specify this property, you must also specify the events that will be handled.
`oninterop_<event-name>`	`function`	Defines a DOM event to be handled by one of the Interop methods specified in the `connected-methods` property. The property name must always be prefixed with `oninterop_` (e.g., `oninterop_my_event`). Accepts as a value the component hook that is defined as the handler for the respective Interop method. You can define as many DOM events as necessary.

The component has the following methods that can be accessed via the this object upon successful connection to the io.Connect framework:

Method	Accepts	Description
`executePlatformMessageCallback()`	`(string, boolean, object)`	Use this method to send a response to the `InteropConnectedComponentStandalone` component about the result from the Interop method invocation. The component will relay the response to the calling app. Accepts three required arguments - the ID of the invocation (which can be extracted from event details), a Boolean value denoting whether the invocation `Promise` should be resolved (`true`) or rejected (`false`), and the actual result from the method invocation to be passed to the calling app.
`isListeningToMethod()`	`(string)`	Indicates whether the derived component is currently enabled to listen for invocations of a specific Interop method. Accepts as a required argument the name of the Interop method which to verify.
`registerMethod()`	`(string, string)`	Can be used instead of the `connected-methods` property to register Interop methods for handling DOM events. Accepts as required arguments the name of the Interop method and the name of the DOM event.
`triggerOutbound()`	`(object)`	Invokes an Interop method registered by other interop-enabled apps. Accepts as a required argument an object with `method` and `payload` properties specifying the name of the Interop method to invoke and arguments for the invocation.
`unregisterMethod()`	`(string)`	Unregisters an Interop method. Accepts as a required argument the name of the Interop method to unregister.
`verifyExistingExternalRegisteredMethod()`	`(string)`	Verifies whether an Interop method is registered within the io.Connect framework. Use this method before invoking an Interop method registered by another interop-enabled app. Accepts as a required argument the name of the Interop method to verify.

Using io.Connect APIs

⚠️ Note that using the io.Connect APIs in your interop-enabled component must always be executed via the onConnected() hook to ensure connectivity to the io.Connect framework.

The io.Connect APIs provided by the initialized @interopio/desktop or @interopio/browser libraries can be accessed directly in your interop-enabled component. This enables you to use all functionalities they provide in addition to the APIs provided by the InteropConnectedComponentStandalone component.

The io.Connect APIs can be accessed only after a successful connection to the io.Connect framework has been established. To ensure this is the case, always route the usage of io.Connect APIs via the onConnected() hook of your component.

⚠️ Note that to be able to use the @interopio/workspaces-api and the @interopio/search-api libraries, you must explicitly enable them via the library initialization configuration in the InteropConnectedComponentStandalone component. If Salesforce is running in io.Connect Desktop, you must also make sure that the @interopio/desktop library won't be auto initialized via the Salesforce App Definition.

Example Implementation

To interop-enable your LWC, you must:

create a standard LWC with XML, HTML, and JavaScript files;
use the InteropConnectedComponentStandalone component in the HTML file to wrap your LWC;
define the required component properties (application-name and factory-config) in the HTML file;
use the InteropConnectedComponentStandalone component API and the io.Connect APIs to implement the component functionality;

The following examples demonstrate how to create an interop-enabled LWC that will be used in an io.Connect Desktop platform. The component registers an Interop method that can be invoked by other interop-enabled apps, and also invokes an Interop method already registered by other interop-enabled apps.

Example XML configuration for a LWC:

<?xml version="1.0" encoding="UTF-8"?>
<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
    <apiVersion>60.0</apiVersion>
    <isExposed>true</isExposed>
    <description>This component demonstrates inbound and outbound interoperability between Salesforce and io.Connect apps.</description>
    <masterLabel>My Interop-Enabled Component</masterLabel>
    <targets>
        <!-- Salesforce pages targeted by the component. -->
        <target>lightning__RecordPage</target>
        <target>lightning__AppPage</target>
        <target>lightning__HomePage</target>
    </targets>
</LightningComponentBundle>

Example HTML structure of an interop-enabled LWC that uses the InteropConnectedComponentStandalone component:

<template>
    <!-- Using the `InteropConnectedComponentStandalone` component to interop-enable your LWC. -->
    <Tick42-interop-connected-component-standalone
        application-name="my-interop-enabled-component"
        factory-config={myCustomIODesktopConfig}

        connected-methods={connectedMethods}
        oninterop_inbound_event={onInbound}
    >
        <lightning-card title="My Interop-Enabled Component">
            <!-- Your component structure. -->
        </lightning-card>
    </Tick42-interop-connected-component-standalone>
</template>

Example implementation of an interop-enabled LWC:

// Import the `InteropConnectedComponentStandalone` component.
import InteropConnectedComponentStandalone from "Tick42/interopConnectedComponentStandalone";

const TEST_INBOUND_METHOD = "My.Test.Inbound.Method";
const TEST_OUTBOUND_METHOD = "My.Test.Outbound.Method";
const DOM_EVENT_TO_LISTEN = "inbound_event";

export default class MyInteropEnabledComponent extends InteropConnectedComponentStandalone {
    // Custom configuration for initializing the `@interopio/desktop` library.
    myCustomIODesktopConfig = {
        // Enabling the Workspaces API and the Search API.
        workspaces: true,
        search: true
    };

    /**
     * Defines Interop method mappings.
     * Each key is an io.Connect API method and each value is the corresponding DOM event it sends.
     * These mappings are forwarded to the `connected-methods` property of the `InteropConnectedComponentStandalone` component.
     * All DOM events related to io.Connect functionalities are prefixed with `interop_` to prevent conflicts with other events.
     */
    connectedMethods = {
        // "My.Test.Inbound.Method": "inbound_event"
        [TEST_INBOUND_METHOD]: DOM_EVENT_TO_LISTEN,
    };

    // If you don't need to customize this hook, you can skip its declaration.
    disconnectedCallback() {
        super.disconnectedCallback();

        console.log("Disconnected callback invoked.");
    };

    // If you don't need to customize this hook, you can skip its declaration.
    renderedCallback() {
        super.renderedCallback();

        console.log("Rendered callback invoked.");
    };

    // This will be called by the `InteropConnectedComponentStandalone` component
    // on successful connection to the io.Connect framework.
    // Once connected, you will have access to all io.Connect APIs via the `this.io` object.
    // You must execute all your outbound Interop logic in the `onConnected()` hook.
    onConnected() {
        super.onConnected();

        // Invoke an outbound Interop method.
        this.triggerOutbound();
    };

    // Implementation of the handler for the `TEST_INBOUND_METHOD` method that will be invoked for the `inbound_event`.
    onInbound(event) {
        // Extract the invocation ID and the arguments for the Interop method invocation provided by the calling app.
        const { callbackID, payload: { value } } = event.detail;
        // If `true`, the `InteropConnectedComponentStandalone` component will resolve the invocation `Promise`.
        // If `false`, the `InteropConnectedComponentStandalone` component will reject the invocation `Promise`.
        const isSuccessful = value ? true : false;
        // Result that will be returned from invoking the Interop method.
        const invocationResult = { "OK": value ? true : false };

        // Send a response to the `InteropConnectedComponentStandalone` component.
        // The `InteropConnectedComponentStandalone` component will relay the response to the calling app.
        super.executePlatformMessageCallback(callbackID, isSuccessful, invocationResult);

        console.log(`Inbound data received: ${value}.`);
    };

    triggerOutbound() {
        // Checking whether the desired Interop method has been registered by any io.Connect app.
        const isRegistered = super.verifyExistingExternalRegisteredMethod(TEST_OUTBOUND_METHOD);

        // Skip the invocation if the Interop method hasn't been registered.
        if (!isRegistered) {
            return;
        };

        // Providing the name of the Interop method to invoke and arguments for the invocation.
        const args = {
            method: TEST_OUTBOUND_METHOD,
            payload: { value: "value" }
        };

        // Invoke an outbound Interop method.
        // Alternatively, you can use the io.Connect API directly: this.io.interop.invoke(args.method, args.payload);
        super.triggerOutbound(args);
    };

    onError() {
        console.error("Something went wrong, check the latest error logs.");
    };
};

Application Adapters Documentation

Salesforce