A table containing document properties. Three columns: name, value and meta data (aka controls) to a property.
This macro contains the document properties in a table. The first column contains the name of the property, the second column contains the value. The value may be a macro to be evaluated. The macro should return a static value. The third column contains controls.
It is very important to note that the property values are used in the Lucene index.
Therefore property values must not contain sensitive (secret) information!
If a page is accessible for a user, all properties of that page will also be accessible for that user.
Here is an example of the macro in edit mode:
Macro Body with a valid Document Properties Table
The following screenshot shows the macro with a valid document properties table:
Document Properties provides information about the standard properties of projectdoc.
The following controls are valid:
- Signals that the property should be transcluded from the delegate document.
- Exports the property as metadata.
- Exports the property as schema information.
- Prevents the property from being displayed. This allows to add properties to use for selection in queries, but hide them when displaying the document.
- Prevents the property value from being disblocked.
- Marks the value of a property as not being a template despite it may contrain a placeholder reference.
- Prevents the property value from being split into a list of values.
- Tags a property to be mandatory.
- Prevents the property from being indexed with Lucene. A property marked with this control will neither be added with a keyword nor added to the body of the document as text.
- Prevents cleanup services from applying their changes to name, value, and controls of a property.
- Renders a property even if the value is blank.
- Allows to specify an alternative value separator.
Note that the macro should be the first element of the document.
Properties within the table may refer to other properties, also long as the property has been defined earlier.
If you copy names and values for your properties table, there may be invisible elements that will prevent projectdoc to recognize your values properly. If for some reason you happen to not match a given value or your queries do not find a specific property, please check your code with the Confluence Source Editor!
See Cannot access Property from a Document for details.
If checked information passed from the space configuration will be overridden by this macro.
Note that every property will be overridden.
If checked the table containing the properties will not be rendered.
For some pages the metadata is irrelevant to the reader or may be rendered by other means. In this case set this flag to true.
Allows to specify a document to delegate to in order to fetch properties and sections. The delegate document is consulted as a backup for properties and sections.
- To transclude a property from the delegate document, use the delegate control.
- To transclude a section, check the the delegate parameter of the Section Macro.
This feature makes it easy to annotate an existing document. If a document should not be edited, e.g. because it is imported after a release, the delegation parameter allows to transclude content from that document and add additional sections.
If you need to transclude parts of a section and also have to add to that section additional information, use the Transclusion Macro.
Available since version 1.10.
Select a rendering mode for the document properties.
The following values are valid:
The properties are rendered in a table. The first column is the property key, the second the property value. Controls are not rendered, since they are not important to the reader.
|definition list||The properties are rendered as a definition list. The property key key is the definition term, the property value the definition value.|
This controls the formatting of the table. The CSS class applied to the table or definition list.
Mandatory Document Properties
The following properties are mandatory to appear in the document properties table:
- Doctype - must be plain text
- Name - optional if Nameless Documents are in use (note that space homepages cannot be nameless)
- Short Description - optional if no overviews e.g. using the Display Table Macro using default selection is used
Especially a missing Doctype property – since version 2.4 also if the macro contains no table – is reported immediately as an error.
This error is also rendered if the language of the site differs from the language defined for the user. Please make sure that the browser's language (or locale) matches that of Confluence (users with write permission typically experience no trouble if their profile has the correct language set). See Language Problem below.
Each page is created based on the site language (more specific: the site locale). If the site language differs from that of the page, the macro is not able to find any document properties.
The language for the whole site can only be configured by an admin.
Example Configuration for German (Deutsch)
Note that this has nothing to do with the Indexing Language of General Configuration. This is typically not changed from its original value (which is English even if the global default language is set to another value).
This is really only relevant for properties that have meaning to the system. Only in this case the system has to translate the name of the property. Other properties are usually passed through without translation. Therefore users may add any number of properties without the need of providing localization bundles (these are resources that contain text for a specific language).
This problem occurs usually, if a space is imported from a site based on a different language. There is no workaround for this problem than translating the pages. This is a problem - to our knowledge - that is shared by all macros that display generated text resources.
A page in Confluence containing generated text will contain this text regardless of any changes of the language after creation. This is similar to any user added text. The user (without the help of third-party plugins) writes text to a page in one language.
If a document has already been created with the wrong language, all property names and sections need to be replaced (for instance the macro is looking for 'Dokumenttyp' since the language is set to German, but the property in the document reads 'Doctype'). This is because a page in Confluence has no reference to the blueprint it has been created with. Often it is easier to create a new page with the blueprint wizard and copy the property values and section bodies from the old to the new document.
Only one Version of the Macro
Please note that there must only be one instance of this macro on a page.
This macro is the working horse of projectdoc. It provides the basic information to transform a Confluence page into a projectdoc document. This allows users to employ automatic lists to display documents by their metadata.
Length of Property Values
The value of a property is stored in the database as an unlimited string (
StringLength.UNLIMITED). It depends on the database of the Confluence installation how large this actually is.
Keep in mind that most clients assume that these values are typically small. The values are also cached for fast access.
The property value should either be text or have a macro that always returns the same value.
Dynamic Content as Property Value - think twice!
If the macro returns dynamic values, the value cannot be used in queries.
Values are stored in the Lucene Index at the time the document is stored. If the document contains dynamic content, changes in the content will not be reflected in the index until the page is stored again.
There is no guarantee that a dynamic value renders the same way in two different situations.
It is important to note that there are use cases where a dynamic property value is used, but these use cases (typically) must not include searching. Therefore the projectdoc Toolbox does not prevent the use of such macros as property values. If you ensure that the values are static in the context of the use case, then you may use a dynamic macro. For example:
- Use a separate space with documents that do rarely change. On every change on documents of that space all depending spaces, that is a space where there a documents with property values that make searches, need to be reindexed.
- It is save to use the dynamic content properties as long as the macros point to properties on the same page.
As a rule of thumb: The Name List Macro (and its relatives) provide static content, while the Display Table Macro or the Display Document Property Macro does not. Since the display property macros keep track of references they are in many use cases safe to use. Searches, like executed by the Display Table Macro and its relatives, should be avoided (and maybe will be forbidden in future versions of the projectdoc Toolbox).
Macros to define document properties.
A table supplying additional document properties from an attached file.
A table containing additional document properties. Three columns: name, value and meta data (aka controls) to a property.
Macros related to the Document Properties Marker Macro.
Renders the value of a document property as an image. The property value is required to an URL that points to an image.
Renders the value of a property of a document.
Displays a single property of a document that is referred by a property of another document and concatenates it with the value of a local property.
Displays a document property from a referenced document.
Renders a template with property references.
Renders a space attribute value.
Renders a space property value.
Lists references to projectdoc documents in a list. List contain names and optional short descriptions.
Lists references to projectdoc documents in a list. List items are defined by templates referencing properties.
Lists references to projectdoc documents in a table. Allows to select document properties for columns. Also non-list representations are provided.
Renders a table of index entries.
Renders transcluded content fetched from documents of a result set.
Renders transcluded content fetched from documents of a result set.
Renders a section, if the body is not empty. Supports authors to create content, clutter-free rendering without empty sections. Allows to transclude the content.
Resources related to the Projectdoc Properties Marker Macro.
- projectdoc Document - projectdoc is based on projectdoc documents. Creating a projectdoc document is easy: A projectdoc document is a Confluence page using document properties and sections.
- Document Properties - Properties are metadata that can be added to every projectdoc document. If you require a set of metadata for each instance of a document type, you should write your own doctype.
- Document Property Controls - Lists valid controls for properties to be used in document properties tables.