{"id":1670,"date":"2017-06-02T09:57:39","date_gmt":"2017-06-02T08:57:39","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=1670"},"modified":"2017-06-27T09:12:08","modified_gmt":"2017-06-27T08:12:08","slug":"defining-heading-tag-document-publisher","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/defining-heading-tag-document-publisher\/","title":{"rendered":"Defining a Heading Tag in Document Publisher"},"content":{"rendered":"

In Document Publisher<\/em> you can define headings in several ways; this post will show how to define the Heading tag<\/em>.<\/p>\n

Before starting, Word’s Multilevel List<\/em> needs to be set; use the list which has Numbering and Heading<\/em> set:<\/p>\n

\"Multilevel
Word Multilevel List options<\/figcaption><\/figure>\n

This will give the user a Heading style<\/em> which numbers the names of the items output.<\/p>\n

Add a ParagraphGroup<\/samp> tag<\/a> and create your Hierarchy table<\/a> and set the Key or Identity in the Item Selection.<\/p>\n

Default Settings for the Heading Tag<\/h2>\n

Placing cursor at the end of the word ParagraphGroup<\/samp> in the tag but before the bookmark, click on the arrow for the Field tag button and select the All item types<\/em> option and then down to Heading<\/em> tag option at the bottom.<\/p>\n

\"Heading
Selecting the Heading field tag<\/figcaption><\/figure>\n

The Field Details UI<\/em> will look like this when it opens:<\/p>\n

\"Field
Field Details User Interface with the default settings<\/figcaption><\/figure>\n

This is where the user sets the Heading tag<\/em> options for each row, starting with the top row. Leaving all the options as set for each row will give the user the following output:<\/p>\n

1 \u00a0Stakeholder Requirements\r\n1.1 \u00a0Customer Requirements\r\n1.1.1 \u00a0Capacity\r\n1.1.1.1 \u00a0Flight Crew\r\n1.1.1.1.1 \u00a0Corrective Maintenance (Air)\r\n1.1.1.1.1.1 \u00a0Fault Monitoring System\r\n1.1.1.1.1.2 \u00a0Pilot\r\n1.1.1.1.1.3 \u00a0Co-pilot\r\n<\/pre>\n
Basing the Heading Level on the Item Attribute Key<\/h2>\n
The user may require that the sections start with a different number for example they may wish to use the key instead for the Heading tag.<\/em><\/p>\n
The Word’s Multilevel List<\/em> is not needed to be set for this option as the numbering is set by the Key.<\/p>\n
Setting the Include level<\/em> to No<\/em> and Count Separators<\/em> to Add<\/em> and the Attribute<\/em> to Key<\/em>, the type of Separator<\/em> will now not use the Hierarchy Level<\/em> in the output but base the numbering on each items Key<\/em>.<\/p>\n
The user can set each of the other rows to the same settings as the top row by select the row, clicking the Remove Field button \"Remove and then the Copy Field button \"Copy.<\/p>\n
\"The
The Field Details using the Key not the Hierarchy Level<\/figcaption><\/figure>\n
This will give the user the following type of output; remember the Key<\/em> starts at 0<\/em> but the Heading numbering<\/em> in the Heading Styles<\/em> starts at 1:<\/em><\/p>\n
1\u00a0 Stakeholder Requirements\r\n2\u00a0 Customer Requirements\r\n2.1\u00a0 Capacity\r\n2.1.1\u00a0\u00a0 Flight Crew\r\n2.1.2\u00a0 Corrective Maintenance (Air)\r\n2.1.3\u00a0 Fault Monitoring System<\/pre>\n
Using the Separator Option<\/h3>\n
This option allows the user to change to which separator is used within Key or attribute the user has decided to use<\/p>\n
Using the include Fixed Number Option<\/h3>\n
The user can use an Include Fixed Number of separators and Add or Subtract the number of separators for a different output. If the user sets it to Add and the Fixed Number to 2, it will add 2 separators to the key and the output will look like this:<\/p>\n
1.1.1\u00a0 Stakeholder Requirements\r\n1.1.2\u00a0 Customer Requirements\r\n1.1.2.1\u00a0 Capacity\r\n1.1.2.1.1\u00a0\u00a0 Flight Crew\r\n1.1.2.1.2\u00a0 Corrective Maintenance (Air)\r\n1.1.2.1.3\u00a0 Fault Monitoring System<\/pre>\n
If the user set it to Subtract and the Fixed Number to 1 the output will look like this:<\/p>\n
1\u00a0 Stakeholder Requirements\r\n2\u00a0 Customer Requirements\r\n3\u00a0 Capacity\r\n3.1\u00a0 Flight Crew\r\n3.2\u00a0 Corrective Maintenance (Air)\r\n3.2.1\u00a0 Fault Monitoring System<\/pre>\n
Note:<\/strong> Don\u2019t use subtract on rows where the key is only a single digit as the numbering will not be output, showing up like this:<\/p>\n
Stakeholder Requirements\r\nCustomer Requirements\r\nCapacity\r\n1\u00a0\u00a0 \u00a0Flight Crew\r\n2\u00a0\u00a0 \u00a0Corrective Maintenance (Air)\r\n3\u00a0\u00a0 \u00a0Fault Monitoring System<\/pre>\n
Using the Hierarchical Level with an attribute<\/h3>\n
The user can use the Hierarchical Level<\/em> with the Key<\/em> which will add the key to the level in the hierarchy and the output will show like this:<\/p>\n
1.1\u00a0 Stakeholder Requirements\r\n1.1.1\u00a0 Customer Requirements\r\n1.1.1.1.1\u00a0 Capacity\r\n1.1.1.1.1.1.1\u00a0\u00a0 Flight Crew\r\n1.1.1.1.1.1.1.1\u00a0 Corrective Maintenance (Air)\r\n1.1.1.1.1.1.1.1.1\u00a0 Fault Monitoring System<\/pre>\n
The other attributes the user can use to the set the level with or without the Hierarchical level<\/em> are Identity,<\/em> Group<\/em> and a Category<\/em>. When Category<\/em> is selected a new option shows to let the user pick the category they wish to use.<\/p>\n
Using the Heading Title Option<\/h2>\n
The Heading Title<\/em> option allows the user to use different sources to name the item being output. The option include:<\/p>\n