End users access in-application support in one of two ways. The first is via a help link, button, or menu item in the recorded target application. This option is called help integration and requires an application administrator to make minor configuration changes in the target application to enable the Player context-sensistive help. The second option, called SmartHelp, is to install a toolbar button in a browser in which a user launches the target application. This is installed as a browser add-on and may require the help and approval of your Information Technology resources.
These are the steps for implementing in-application support. You may or may not need to perform all of them, depending on the target application that your audience will be using.
Refer to the following table to determine the method your application supports.
Target Application |
SmartHelp |
Help Integration |
|---|---|---|
Agile PLM |
|
X |
CA Clarity PPM |
X |
X |
CA Service Desk |
X |
|
JD Edwards EnterpriseOne |
X |
X |
JD Edwards World |
|
X |
Microsoft Dynamics CRM |
X (ver. 4 only) |
X |
Oracle (Siebel) CRM On Demand |
X |
|
Oracle E-Business Suite |
X |
X |
Oracle Fusion |
X |
|
Oracle (Hyperion) EPM |
X |
|
Oracle Transportation Management |
X |
|
PeopleSoft Enterprise |
X |
X |
SAP GUI for HTML |
X |
X |
SAP GUI for Windows |
|
X |
SAP NetWeaver Portal |
X |
X |
Siebel CRM (On Premise) |
X |
X |
Other Browser-based applications |
X |
|
Note: SmartHelp is available for Browser-based applications as long as the toolbar is available.
Refer to the following information for the general steps to implement SmartHelp or help integration.
Implement SmartHelp
Implement Help Integration
Details about each step are in the following sections.