Contact us Blog

Using Apsona with Salesforce Lightning

Overview

With a few exceptions, Apsona provides all its functionality within the Salesforce Lightning Experience. When you click the App Launcher in Lightning, Apsona is available as a choice in the apps popup, and clicking it will display the Apsona screen under the main menu, as expected.

Opening Apsona in a new browser tab

When running under the Lightning experience, Salesforce displays a menu bar at the top, and that uses additional screen space that you might want to avoid. For this reason, Apsona provides a "pop-out" button that, when clicked, opens Apsona in a new browser tab without the Salesforce menu bar. See screen shot below. This might also be useful when you want to retain an open Apsona window within which to work, while using other tabs to navigate within Salesforce.

Known issues and limitations

The following are the known limitations under the Lightning Experience.

JavaScript buttons unavailable

JavaScript buttons are not available in the Lightning experience. Therefore, to use Apsona's document merge buttons within Salesforce detail pages, you will need the Apsona Lightning component.

Document object unavailable

The Document object is not available in the Lightning experience, so when using Lightning, you will not be able to upload a document template for use with the Document generator. One way to resolve this issue is to use the Apsona Documents view to manage, upload and replace Documents. The other way is to switch to the Classic experience before doing the upload.

Clickjack protection

The Apsona page displays completely empty if you enable clickjack protection for the Apsona Visualforce page. For the same reason, the Lightning component button for generating documents also fails silently, with no errors. The workaround is to disable clickjack protection for the page.

You can access the clickjack protection setting in the Lightning experience by clicking Setup - Security - Session Settings, and scrolling down to the Clickjack Protection section. See screen shot below. Notice that you need to un-check just the box that says "Visualforce pages with headers disabled". Typically, this limits this setting specifically to application pages from Salesforce partners whose pages are hosted on secure Salesforce subdomains separate from the main Salesforce domain.