Documents have a set of properties which can be read and/or set in the Document Editor. A complete history of every Document is automatically maintained. A new revision is created in the repository each time a Document is modified and saved. Revisions can be easily compared.
Documents have the following properties which are displayed in the Properties panel of the Document Sidebar:
Name - the name of the document
Author - the user name of the person who created the Document.
Revision - the current repository revision number of the Document.
Auto-Suspect - flag that determines if new Work Items created in the Document are automatically marked as Suspect.
If this Document property is enabled in the Document, the Suspect attribute will be applied automatically to child Work Item links, if the parent Work Item is modified. (This setting takes effect when you Suspect Default State and User Guide: Suspect Links.the Document.) The Auto-Suspect works for Document Work Items even if Auto-Suspect is not enabled in Administration. The Suspect flag set on Work Items can be useful for change impact analysis. For more information, see Administrator's Guide: Configuring Work Items:
The Suspect attribute is only applied to links to Child Work Items. (Not to Parents or Structural links within a document.)
See Suspect Links for details.
On-demand Work Item Loading is a new feature that dramatically increases the response time when editing large documents. Because it only loads the Work Items that are scrolled into view, it makes editing large documents more fluid and user friendly.
With 17 On-demand Work Item Loading is now enabled by default, for documents containing 200 or more Work Items.
It can still be turned in its Document Sidebar.or for any document
Administrators can set system-wide behavior by editing the following property in the
200 - The default setting. Enabled for all documents containing 200+ Work Items. (Administrators can set any numerical value.)
true - Will enable it by default for all documents.
false - Will disable it by default for all documents.
There are currently some limitations that occur with On-demand Work Item Loading :
When On-demand Work Item Loading is turned , make sure that all the Work Items you wish to copy have finished loading before pasting them somewhere else within the same document.
(This limitation does not apply when copying them to a different document.)
Caption numbers are sometimes replaced with "#" while viewing the document in Polarion. The "#" are replaced with the correct numbers when the document is exported. See the Caption section for details.
On-demand Work Item Loading can be set to for a document in the Document Properties Sidebar.
Select the target document in the Naviagtion bar.
Click on the top right.
(The Document Properties sidebar appears on the right.)
Click theor button in the Section.
Polarion automatically maintains a history of each Document. Every time you save the Document, a new entry, or revision, is created in the history. You can easily review any revision, and you can compare any two revisions to understand what changes took place between the older and the newer revision.
History is maintained in the underlying Subversion repository. Although developed as a version control (a.k.a. source code control) system, Polarion uses Subversion's history capability to maintain a history of many types of development artifacts, including Documents.
Each revision of the Document is automatically assigned a unique numerical ID, and is stamped with the date and time the revision was written to the repository. If you know the revision number you want to see, you can use your browser's Find feature to locate it on the Document history page. In addition to the date and time, the Document history page shows how long ago each revision took place.
In the history page, you can browse the table of revisions until you find one you want to view. Then click Show in the Actions column. The document loads in the editor in the state it was when the revision was saved, but the content is read-only and cannot be changed.
If a document revision is opened that contains a block of Wiki syntax, but a historical index of the database is currently in progress, then the block’s content will not be displayed until the indexing is complete. While the historical indexing is in progress, the following warning message appears:
You can use thebutton to return to the current state of the Document in the editor.
Baseline revisions that do not match will have the revision number and name rendered in italics in all link states (normal, hover, selected).
You can compare any two revisions in the Document history page. You cannot compare more than two revisions at once.
To compare Document revisions:
Open the Document history page (see Viewing Document History).
In the Revision # column, check the boxes on the rows of the two revisions you want to compare and then click the button.
There are two content states that can be compared:
Document: compare the state of textual content in the two revisions
Work Item: compare the state of Work Items defined in the document in the two revisions.
You can jump between changed elements or Work Items using the Changes buttons at the right side of the history page header. Return to the history page using the button.
When cells that contain text are merged then compared with a previous version, the layout will appear a little strange in the comparison view.
That's because it's more important to view the actual changes than display the layout correctly in comparison view.(This only affects the comparison view. When exporting or viewing the most recent, merged cell revision, or the historical revision before the merge, both layouts will appear as expected.)
After comparing two revisions, you can export the comparison result to PDF. You can only export the Document (content) view.
To export Document comparison results to PDF:
Compare 2 revisions as described earlier.
If you are in the Work Items view, click thebutton on the toolbar to return to the Document view.
In the Document view, locate the Actions Menu button on the toolbar, click it, and choose .
In the Export to PDF dialog, set the export options as desired and click .
The Outline panel of the Document Sidebar displays a hierarchical tree of the Document's headings, including titles of contained Work Items. The Document outline can help you browse the Document structure to some specific part of a Document. Every node is "live" - clicking a node scrolls the Document content to the respective heading or Work Item. When you are editing content in the Document body, the nearest parent heading or title is selected in the Outline panel.
If the outline is large you can enter some text in the edit control provided to filter the outline for the input text. If you add or remove content in the Document, you can use the Update button to refresh the outline tree.
For more information see User Reference: Documents: Documents Reference: Document Sidebar: Document Outline Panel.