Additional Options

communities classic and lightning communities (such as 'napili' and the latest templates) are fully supported for classic, 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 for lightning, community layouts can feature our lightning components, much as with internally facing pages visualforce pages improved help enables help enabling of 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 – so improved help behaves the same way on standard page layouts and visual force pages made to look & feel like standard pages so, the page developer has more flexibility over page layout and the way any apex form tags are used general html ‘non apex’ tags; tabular apex tags apex detail tag a full standard page in classic tabular layout; apex page blocks together with their enclosed, tabular apex field tags; individual non tabular apex tags within more free form page designs please see the resources attached to this topic for further information salesforce mobile (salesforce1) setup improved help for mobile (salesforce1) all that’s needed to setup salesforce1 improved help is to go to setup – build – customize – chatter – publisher layouts edit the global layout; add ‘improved help’ action; save that’s it! any improved help content you have created will now be available to your salesforce1 users in the appropriate contexts for more information, please see the resources attached to this topic service console 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 for full details, please see the resources attached to this topic ed help features internationalisation 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 ('translatables') 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 translatables and can be used to show where each is used within the app each translatable appears in english, with an adjascent 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