Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
titleNew and Noteworthy


Section
titleArtificial Document Properties on Metadata

This release collects metadata to allow 

Static Document Link
documentPDAC:Documentation Gardener
labeldocumentation gardners
 to find referencing documents easier.

Information on property names, controls, and values is collected as well as on document part identifiers and tags.

The following artificial properties support queries for documents that define a given name.

Display Table
doctypedocument-property
selectName, Short Description, Since|
where$<Type>=[projectdoc Metadata Property Definition]

The following artificial properties support queries for documents that use a given name by reference.

Display Table
doctypedocument-property
selectName, Data Type|, Short Description, Since|
where$<Type>=[projectdoc Metadata Property Reference]

More information on this topic is available at 

Static Document Link
documentName Refactorings
.

A reindex is required to add the new properties (see Upgrade Instructions below).


Section
titleTasks Report Macro

The new 

Static Document Link
documentTasks Report Macro
 allows to select Confluence Tasks from
Static Document Link
documentprojectdoc Document
labelprojectdoc Documents
 selected by a Where constraint.

The new macro simply configures the Confluence Task Report Macro and executes it. The new macro is not a replacement. In case users want to select on spaces, pages, and labels, the original macro is still in charge. The new macro simply connects projectdoc documents to the world of Confluence Tasks.


Section
titleSection Compilations

In software product documentation there is a good chance to encounter elements that are reused. For instance a parameter of a collection of macros. Suppose there is a collection of macros that 

Static Document Link
documentPDAC:Transclusion
labeltransclude
 content from a single document. Each of these macros would provide a parameter named "Document" to link to the document to transclude from. Often the documentation for this parameter is identical. Therefore the documentation for the Document Parameter is in one location and the macros transclude this content.

The macros may need to control the order of their parameters. Maybe the first macro has the Document Parameter as its second parameter while all others specify it as their first.

In addition to that some macros may provide parameters they do not share with other macros. So 

Static Document Link
documentPDAC:Author
labelauthors
may want to document these parameters in sections on the macro documentation document.

In this use case the 

Static Document Link
documentSection Compiler by Reference Macro
 is of great support. The body of the macro holds the sections that document parameters the macro does not share. These sections may be in any order. The Section Compiler by Reference Macro references a property that defines the order of all parameters that are to be included in the macro document's documentation. Each reference may refer to a document that contains share information about a parameter or a section in the macros body.

This way it is very easy to mix and merge parameter documentation that is shared with information that has been defined locally.


Section
titleUsability Enhancements

Static Document Link
documentAutocomplete
labelAutocomplete support
 is increased by supporting 
Static Document Link
documentPDAC:Transclusion
labeltransclusion
references (
Jira
serversmartics JIRA
serverId79ad43bc-d289-364e-bfc7-46c09847bebd
keyPDAC-1315
) and property names in drafts (
Jira
serversmartics JIRA
serverId79ad43bc-d289-364e-bfc7-46c09847bebd
keyPDAC-1312
).

The property name for the 

Static Document Link
documentDisplay Document Property Macro
 is now a mandatory property (
Jira
serversmartics JIRA
serverId79ad43bc-d289-364e-bfc7-46c09847bebd
keyPDAC-1314
). Although the default would still be the name of the referenced document, by enforcing to specify a name the macro editor automatically pops up. Since the reference is often not to the name property, this update does better support the usability.

For Scroll Word Exporter (formerly known as Scroll Office) the projectdoc Toolbox now autodetects the required 

Static Document Link
documentPrint Quirk Modes
labelquirk mode
(
Jira
serversmartics JIRA
serverId79ad43bc-d289-364e-bfc7-46c09847bebd
keyPDAC-1324
).


...