This release adds three macros to make it easier to create links to  in your Confluence.

The 

The advantage using the link macros is the rendering of a tooltip on mouse over. The default tooltip text is the short description of the referenced document.

Another use case is rendering links using a publishing process. Typically there is a set of spaces with which the team works. At publishing time the content of some spaces is copied to the published spaces. Dynamic links allow to render the correct links dependent on the 

The following table lists the supported parameters of the three macros.

Use Case	Parameter	Static Link Macro	Dynamic Link Macro	Term Link Macro
Link whole document	Page / Title	Document (Page)	Document Title (Title)	Term (Title)
	Space Closure
Link into document	Anchor
Control label	Label
	Lower Case
	Tooltip
	Abbreviation Mode
	CSS Classes
Document creation	Link Rendering Control
	Blueprint
Remote Control	Request Parameters
Toggle Feature	Request Toggle Label
	Request Toggle Tooltip

Since the Static Link Macro is referencing a document similar to a Confluence link by space key and page title, there is no need to specify the space key separately. There is also no need to specify the space closure. All other use cases are supported.

The Term Link Macro is designed for simplified use and therefore does not provide parameters for use cases beyond rendering a reference to an item in the glossary. Although a space key is required to calculate the link to a document, the macro does not allow to specify the space closure as a parameter. The delegate space is required to be set correctly. This requires that a space defines its 

The projectdoc Toolbox provides a number of macros that allow to automatically link to documents at the moment they appear. This includes the 

With this version the 

The use case for this feature is for template authors. Consider a doctype that is in a close relationship to another doctype, such as a lifecycle and its phases. A phase does reference the lifecycle it belongs to and the lifecycle lists all phases it contains. So a typical location for a phase document would be a child of a lifecycle document. By the use of the Child Documents Macro and Name List Macro the links from a lifecycle to its phases and from a phase to its lifecycle can be automatically created. Since a phase may also be commonly used a number of lifecycles, the value of the lifecycle property of a phase document is required to use the Name List Macro to manually add the names of valid lifecycles where this phase is used.

The 

This feature also updates links in Name List Macros on creation, rename, and deletion of documents.

This feature requires a reindex of the projectdoc Confluence cache. Please refer to 

The following issues enhance the support of the Autocomplete Feature in macros.

1. Jira
   server smartics JIRA serverId 79ad43bc-d289-364e-bfc7-46c09847bebd key PDAC-1286

2. Jira
   server smartics JIRA serverId 79ad43bc-d289-364e-bfc7-46c09847bebd key PDAC-1287

3. Jira
   server smartics JIRA serverId 79ad43bc-d289-364e-bfc7-46c09847bebd key PDAC-1288

4. Jira
   server smartics JIRA serverId 79ad43bc-d289-364e-bfc7-46c09847bebd key PDAC-1281

5. Jira
   server smartics JIRA serverId 79ad43bc-d289-364e-bfc7-46c09847bebd key PDAC-1289

6. Jira
   server smartics JIRA serverId 79ad43bc-d289-364e-bfc7-46c09847bebd key PDAC-1293

With this version users may override any 

Artificial properties are automatically created by a predefined name, such as 

With this version artificial properties are only created if a property by this name does not already exist.

For the properties named Email and Team Email with e-mail addresses as values, now provide a normalized (the plain email address) and a text version (the label of the link) is now supported.

With this version aggregated values collected via