Context-sensitive help systems assist users by providing specific informational topics for certain components of a user interface, such as a button or window. This mechanism works based on mappings between a unique ID defined in the topic and a corresponding HTML page.
<appContext> element, as in the following
example:<map productID="oxy-webhelp" productVersion="1.1">
<appContext helpID="myapp-functionid1" path="tasks/app-help1.html"/>
<appContext helpID="myapp-functionid2" path="tasks/app-help1.html"/>
. . .
</map>The possible attributes are as follows:
A Unique ID provided by a topic from two possible sources
(<resourceid> element or @id
attribute):
<resourceid> element is mapped into the
<appContext> element and can be specified in either
the <topicref> within a DITA map or in a
<prolog> within a DITA topic. The
<resourceid> element accepts the following
attributes:"").@appid
attribute is used.@appid values can be associated with a
single appname value (and multiple
@appname values can be associated with a single
@appid value), but the values for both attributes work
in combination to specify a specific ID for a specific application, and
therefore each combination of values for the @appid and
@appname attributes should be unique within the context
of a single root
map. For example, suppose that you need two different
functions of an application to both open the same WebHelp page.Example: The <resourceid>
Element Specified in a DITA Map
<resourceid> element can be specified in a
<topicmeta> element within a
<topicref>.<map title="App Help">
<topicref href="app-help1.dita" type="task">
<topicmeta>
<resourceid appname="myapp" appid="functionid1"/>
<resourceid appname="myapp" appid="functionid2"/>
</topicmeta>
</topicref>
</map>Example: The <resourceid>
Element Specified in a DITA Topic
<resourceid> element can be specified in a
<prolog> element within a DITA
topic.<task id="app-help1">
<title>My App Help</title>
<prolog>
<resourceid appname="myapp" appid="functionid1"/>
<resourceid appname="myapp" appid="functionid2"/>
</prolog>
...
</task>For more information about the <resourceid> element,
see DITA Specifications:
<resourceid>.
<resourceid> element is not declared in the
DITA map or DITA topic (as described above), the
@id attribute that is set on the topic root element is
mapped into the <appContext> element.contextId value and will look it up in the XML file.contextId parameter with a specific value. The WebHelp
system will automatically open the help page associated with the value of the
contextId
parameter.cshelp.html?contextId=myDITATopiccontextId parameter is not
case-sensitive.You can use the URL field in your browser to search for topics in a context-sensitive WebHelp system with the assistance of the following parameters:
contextId parameter to jump to
a specific section in a document. For example,
contextId=topicID#anchor.contextId to search
for this value in the corresponding appname attribute value in the mapping
file.http://localhost/webhelp/cshelp.html?contextId=topicID&appname=myApplicationwebhelp.csh.disable.topicID.fallback parameter can be set
true to use a topic ID fallback when resourceid information is not
available when computing the mapping for context sensitive help.