With this version property macros (e.g. Display Document Properties Macro or Display Document Property Macro) support phantom references.

This change does change the semantics of references. A document references another document regardless of the existence of the referenced document.

The default use case for the PDAC1 assumes that there is a page blueprint for each doctype. But users employ user templates instead of writing page blueprints.

To serve this group of users better, we decided to add support for document title and document name syncing. projectdoc is based on projectdoc documents. projectdoc documents require a name. Other than the document title, the document name does not need to be unique within a space. Nameless documents still require a name, but it does no longer be explicitly set. The name can be derived from the document title.

Prior to version 2.1 of the projectdoc Toolbox the title only was derived from the name, typically adding some more characters to the title to meet the uniquness constraint. With version 2.1 users may set a title and have the same character sequence also for the name (which makes the name unique). In addition to set a regular expression can be used to derive a name from the page title. The regular expression can be set on space level with a space property for all documents or just for specific document types.

Space properties to configure nameless documents are

1. projectdoc.doctype.*.document.name-pattern
2. projectdoc.doctype.(doctype).document.name-pattern
3. projectdoc.doctype.*.document.name-pattern.group
4. projectdoc.doctype.(doctype).document.name-pattern.group

The Name List Macro provides a new UI to keep the table row height in the document properties table in edit mode smaller.

Based on phantom references the execution for a delete tree is much faster due to optimizing the number of documents that need to be updated.

Reindexing of documents is now based on queueing implementations which makes saving documents quite fast.

If you need to combine the results of a Display Table Macro and a manually defined list of entries - for instance by use of the Tour Macro, the new Table Merger Macro allows to render multiple tables in just one table. It also allows to select on and rearrange table columns. The macro can include tables from any source, which includes tables transcluded with the Transclusion Macro.

The Table Set Macro applies a simple set operation on tables in its body. This way authors may run operations like and, or, and not on tables.