<h1>Hello World</h1>
or: <more "HowNCHBWorks">Preparations, How the Help Builder works</more>
The disadvantage of this form of specification is that when changes are made in the structure or the arrangement and grouping of the help topics in the table of contents, all headings and links affected by them must also be updated. Especially with larger online helps, this approach quickly leads to errors and is time consuming.
With the index-driven approach these problems can be avoided as the text displayed is determined by the table of contents. If the structure or the arrangement and grouping of the help topics in the table of contents is changed later, the topic headers and topic links do not need to be changed additionally.
<h1>Hello World</h1>
you can simply specify the placeholder <iheader>: <h1><iheader></h1>
The online help later displays the text specified in the table of contents instead of the placeholder.
Note
In the Preview only the text <Index-driven Header> is displayed.<more "HowNCHBWorks">Preparations, How the Help Builder works</more>
the i variant no longer needs text: <imore "HowNCHBWorks">
The online help later displays the text specified in the table of contents.
Note
In the Preview only the text <Index-driven Link> is displayed.Example | Becomes |
---|---|
<ilink "HowNCHBWorks"> | Preparations, How the Help Builder works |
<imore "HowNCHBWorks"> | For more information, see Preparations, How the Help Builder works. |
<ilinkshort "HowNCHBWorks"> | How the Help Builder works |
<imoreshort "HowNCHBWorks"> | For more information, see How the Help Builder works. |
Note
<imore automatically adds a dot to the end of the link. This can be prevented by using <imore+NCCA Cost Accounting Cost Accounting - up to 8 dimensions, allocations with many variants, comprehensive evaluations. More information AppSource |