Versions Compared

Key

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

...

Section
titleNew and Noteworthy


Section
titleEnhanced Space Properties

Properties that define the space closures can now be defined in space properties extensions.

This is an important feature for publishing processes. Now all space specific properties can be collected on a separate page that is treated different from other published pages.

Space properties are also rendered, therefore macros can be used in more space property values.

For more information see 

Jira
serversmartics JIRA
serverId79ad43bc-d289-364e-bfc7-46c09847bebd
keyPDAC-1222
.


Section
titleMaterialize Properties

This new version allows template authors to easily materialize values by the use of the mat document property control.

Materialization can also be controlled by the space property named Materialize by Doctype.

This allows the use of Deep Links on the left side of a Where constraint (see Search Tips).


Section
titleRemote Controlling Macros

Transcluding macros now take advantage of the Remote Control feature. By the use if Remote Controls these macros configure the context of the rendering process and alter the rendering result.

The following macros support remote controls (the Wiki Link Macro supported this feature in the past and does so by the use of HTTP request parameters):

Display Table
doctypemacro, app-macro
render-modedefinition
where$<Tags>=[Remote Controller]
space-keyPDAC1


Section
titleToggle Feature for Wiki Links

The Wiki Link Macro allows, based on its Remote Control Parameters, to toggle between two states. Since the macro is now also allowed to reference the document it is part of, this feature can be used to toggle between two views of the same page.

A typical use case is to have a condensed and another expanded version of a table.

The tip Toggle Views shows this use case in some detail.


Section
titleMatch Pattern for Display Property Macro

There are new parameters for the Display Document Property Macro that allow to define a match pattern by a regular expression and use the matched groups in a template.

This new feature allows users to grab parts of a property value and reuse its parts in its own value. For instance: if you document a product which has the version number in its name, then the short name could be defined as the name without the version. So in case the name is changed, the short name is updated accordingly.


Section
titleEmpty Content

The Content Marker Macro and Section Macro may now be tagged as being empty. This allows wrapping containers to control more specifically to hide if all its content is considered to be empty.

This is the generalization of the Ignore Template Buttons where a section is considered empty if this button is the only visible element inside a content marker or section.


Section
titlePretend being a Printer

In previous versions the only way to switch to printer mode to export Confluence pages to PDF or Word has been to set the user space property Pretend Being A to the value 'printer'. This has been only possible for users who created a user space for their own.

With this version the mode is automatically selected in case the output type of PDF or Word has been selected. This new feature not only makes it much easier to switch to printer and activate quirk modes, but makes this feature also available to users without a user space.


Section
titleTemplates for Tour Macro

With this version the header column may contain a template to render multiple properties in one column.

Use the standard syntax to define a template.

Code Block
languagetext
#T{$[Name] (${Type})}

Use the column translation parameter to specify the column header label.


Section
titleArtificial URL Property Values

The URL and Tiny URL artificial properties now follow the following semantics.

PropertySemantics
URL, Tiny URLThe URL as an HTML anchor element.
URL$, Tiny URL$The label for the URL.
URL§, Tiny URL§The plain URL.

These semantics already have been applied to other URL properties.

Here is more information on 

Static Document Link
documentArtificial Properties
 and
Static Document Link
anchorUniform Resource Locators
documentArtificial Properties
labelURLs of artificial properties
.


Section
titleImprovements to Property Controls


Section
titleEditing Property Controls

The REST services now allow users to edit document property controls. Please updated to the latest version of the Web API Extension (see

Jira
serversmartics JIRA
serverId79ad43bc-d289-364e-bfc7-46c09847bebd
keyPDEXWAPI-48
) to take advantage of this improved service.


Section
titleClean Controls

Document property controls are now cleaned from HTML elements per default.

Pasting a property control with the Confluence editor often not only copies the control string, but also HTML elements, like span with some CSS attributes. While the additional HTML markup is often not easily perceived by users, the parser does not recognize the control, assuming that the additional HTML elements are of significance.

We now assume that there is no need for users to add markup to the controls column of their Document Properties Marker Macro (or related macros). Therefore we remove them before parsing the control strings.



Section
titleHomepage Links

The Wiki Link Macro provides style clues on whether or not there are documents of a given type in the current space or if this information is delegated to another space.

This version provides some improvements so that this information is working more intuitively out-of-the box. See 

Jira
serversmartics JIRA
serverId79ad43bc-d289-364e-bfc7-46c09847bebd
keyPDAC-1225
Jira
serversmartics JIRA
serverId79ad43bc-d289-364e-bfc7-46c09847bebd
keyPDAC-1226
, and 
Jira
serversmartics JIRA
serverId79ad43bc-d289-364e-bfc7-46c09847bebd
keyPDAC-1227
  for more information.


Section
titleREST Services for Auto IDs

We now provide some internal services to have access to the configuration of Auto IDs. While this is still an internal API – and therefore subject to change without notice – it may be a valuable tool for users who need to see the actual configuration.


Section
titleUnlicensed Rendering

The Section Macro and Content Marker Macro render their body even if there is no license provided. This allows users to still see their content in the web view after the license expired.

When no license is provided the macro parameters and the body is rendered.

Here is an example of a page rendered without license.

The section Child Documents shows the text content and some macros used in its body. For the Display Table Macro only the configured parameters are rendered. For the Tour Macro besides the macro parameters the body (with a table) is also rendered.

Note that it is only guaranteed that the body and parameters will be visible. All other features of the projectdoc Toolbox may or may not work.


...