This page contains additional options for customising Embedded Help.

Classic and Lightning Communities (such as 'Napili' and the latest templates) are fully supported:

, our 'help hooking' components can be added to the shared scripts of an entire community or particular areas / pages as desired, bringing the Quick Access Menu and / or embedded help to community users.

, community layouts can feature our Lightning components, much as with internally facing pages.

You can help-enable any HTML tags in the helped Visual Force page. Typically, pages will include Apex tags for data display and/or entry, and some of these may be placed in Apex tabular page blocks to provide a user interface like standard classic pages.

Where tabular Apex form tags are used, Improved Help’s hooking mechanism recognises the rendered page markup and provide automated support of help callout positioning and sizing. As such, Improved Help behaves the same way on standard page layouts and Visual Force pages made to look and feel like standard pages.

In this way, the page developer has more flexibility over page layout and the way any Apex form tags are used:

: A full standard page in classic tabular layout;

: together with their enclosed, tabular Apex field tags;

Setup Improved Help for Mobile (Salesforce1)
All that’s needed to setup Salesforce1 Improved Help is to:

Setup > Build > Customize > Chatter > Publisher Layouts

Save to finish. Any Improved Help content you have created will now be available to your Salesforce1 users in the appropriate contexts.

Provide a Quick Access Menu and embedded help for your Console users. For each Page Layout you will need to create a new button or custom link, which will reveal embedded help for the tab:

Use a button if you would like embedded Help to appear only when users request it: they click the button to switch on Help if they wish to each time they refresh the tab.

Use a link if you want embedded Help to appear automatically for a given layout.

The Improved Help App ships with numerous custom Objects, Classes and Visualforce pages, each of which generate various on-screen labels and feedback messages. Our internationalisation features allow Orgs to provide their own translations for all of these elements (

) by following a single, consistent, easy to use process:

Orgs can use our free, Excel-based translation tool (the 'Locale File Generator') to produce localisations.

Create one copy of the tool for each desired language. The tool contains a listing of all Help 

 and can be used to show where each is used within the App.

Each translatable appears in English, with an adjacent cell for the Org's desired translation.

Once all translations have been entered, the tool provides the means to produce Help-ready localisation XML (a 'Locale File').

Upload the Locale File to the Improved Help Documents folder, naming it according to the language it serves (see details later in this Reading List).

Help will seek translations in the Locale File appropriate to the logged in User's selected language: if no suitable file has been uploaded or particular translations are missing, default (English) values are used.


Explore additional options in Unaric Guide to customize components: Communities, Visualforce pages, Service Console, and more.

Customer Style Sheet

Additional Options

Documentation created by Authors for display in Salesforce.

Help_Topics

Version

Include Help in Wrapper Components

Control Components Via Events

Deployment Examples

Unaric Guide

Guide

Overview

NoticeBoards Setup

Sandbox Migration Checklist

Embedded Help Setup

Getting Started