BrainStorm Cool Tip: Automatically Updating Headers

By: coolguys

April 13, 2006 12:00 am





Welcome to BrainStorm Cool Tips. New tips will be posted regularly to help you more effectively use GroupWise. If you have any suggestions for tips, please feel free to let us know by emailing

After you learn to use’s templates and styles, a new world of formatting possibilities opens, especially in the Word Processor. Here’s how to take advantage of one of those possibilities: Automatic Headers.

  1. Select Tools –> Outline Numbering.

  2. Click the Numbering tab.
  3. In the Paragraph Style pulldown menu, select the paragraph style you have applied to the headings you want to automatically appear as headers. (If your headings are set as “Chapter Title,” select “Chapter Title.”)
  4. Click OK.
  5. Place your cursor in the heading area of a page with the page style that will include these headers.
  6. Select Insert –> Fields –> Other.
  7. Click the Document tab.
  8. In the Type box, select Chapter.
  9. In the Format box, select Chapter name.
  10. Click Insert.
  11. The text of your most recent heading will appear in the gray field.

  12. As you continue to create the document, anything assigned that heading style in the main body of your document will appear in the header field.

When you set your own Outline Numbering by following the first four steps of this tip, you have also set up your document to automaticallly create Tables of Contents, to display heading levels in the Navigator, and to create other automatic fields such as bookmarks and cross references.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized

Disclaimer: As with everything else in the SUSE Blog, this content is definitely not supported by SUSE (so don't even think of calling Support if you try something and it blows up).  It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.