The Application Instances section allows you to configure the applications and connect them with the sources you configured in the Sources section. The options vary, depending on whether the application supports SmartHelp only, SmartHelp and Help Integration, or help integration only. See Implement In-Application Support for a list of applications.
In the Type list, there are two non-specific application options listed: Browser Application and Custom Application. A browser application is exactly that - an application that runs in a browser window. This type of application is only enabled for SmartHelp. A custom application is one that you have created using the SDK. It may be available for either or both SmartHelp and Help Integration.
Type: Choose the application type from the list.
Name: Enter a user-friendly name for the application instance.
Application Namespace: This option only appears if you selected Custom Application from the Type list and your application implements the In-Application Support SDK. This is the name created in the SDK when context-sensitivity was created. It should be in the form of app.<namespace>, for example app.com.example.MyApplication. See the In-Application Support SDK guide for more information.
Options for SmartHelp-Enabled Applications
SmartHelp Sources: This is list of sources that have been enabled for SmartHelp in the Sources section. Select the sources to be automatically searched by SmartHelp when the user is working with this application instance.
SmartHelp URL Rules: Specify the URL of the server for the application. If there are multiple URLs, you can add new ones as needed. See SmartHelp URL Rules following this section for more information.
Options for Applications that Support Help Integration
These options allow you to configure a gateway page that launches when a user clicks the Help link. You can also configure the gateway page to give the user access to additional resources, such as the original help for the target application, additional Player packages, or a URL to another web site. See application sections for application specific configuration options and configuration steps.
Default Player: This is the Player that launches if you do not configure the gateway page. If you configure any kind of content segmentation, such as multi-language support, it only applies to this Default Player, not to Players launched from other tabs or links. It also specifies the source so that the configuration for this application is published when the outline referred to by the source is published.
Segment Players: These options allow you to configure the help to launch the appropriate content if you have developed content in multiple languages, called segmentation. For each Segment Player, you choose the content from the list and then specify a language code. The language codes you use should match the ones used by the application. Some applications may have additional options.
Note: The list is searched in the order you specify, and the first matching Player is launched.
Help Integration Additional Tabs: Allows you to create more tabs in the gateway page to display other Players, the original application help, or the target of a URL. Choose the source from the Tab 1 list. Use the add new link to add a tab, and a new Tab option appears in which you can choose the source for that tab.
Remember Active Tab: If this option is selected, a cookie is placed on the user's system so that the gateway page launches with the tab that was active when the user last accessed it.
Help Integration Additional Links: You can create links as well as tabs. Tabs are opened in an iFrame inside the gateway page, while links open a new window. Links are needed when a page does not allow being embedded in a page and must be opened in a standalone window. In the Link Menu Title field, enter the name of the link menu text to appear on the gateway page. From the Link 1 list, choose the source for the link. Use the add new link, and a new Link option appears in which you can choose the source for that link.