Page tree

Versions Compared

Key

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

...

Section
titleNew and Noteworthy


Section
titleData Center Compatibility

To save resources on a Data Center installation of Confluence, macros are required to limit the number of hits processed in one request.

Since the projectdoc Toolbox is intended be used to design documents to be exported to formats like PDF, paging is not supported by most macros. If the result set generated by a macro is larger than the configured limit, dependent on the macro either a warning or an error is rendered. Users are required to adjust their queries to pass the limit test.

The following macros are also affected by this limitation.

Tour
header-translationsTitle=Macro
replace-title-with-nametrue



The following macros process tables and will render an error message if the underlying macros render a warning message.

Tour
header-translationsTitle=Macro
replace-title-with-nametrue



Administrator configure the page size, which defaults to 100, via the administration screen.

Not that also the Web API is limited by the page size. The Web API supports paging.

For more information, please refer to 

Static Document Link
documentLimitations on Query Results
.


Section
titleData Center Support

The following apps are approved to be used on Confluence Data Center.

Section
titleExtensions

The following extensions are available for Confluence Data Center and Confluence Server.

Tour
header-translationsTitle=Doctype Add-on





Section
titleDoctype Add-ons

The following doctype add-ons are available for Confluence Data Center and Confluence Server.

Tour
header-translationsTitle=Doctype Add-on




The following apps are currently not provided for Confluence Data Center. The Maven Extension will not be supported because it relies on libraries which are not updated regularly and the extension is considered unfit to meet the requirements imposed by a data center installation. It may still be used in some use cases.

Section
titleExtensions

The following extensions are not provided for Confluence Data Center.

Tour
header-translationsTitle=Doctype Add-on


TitleRemarks
Bookmarklets ExtensionMay be available in the future
Maven ExtensionIs only available for Confluence Server




Section
titleDoctype Add-ons

The user base is considered to small to continue the support of these doctype add-ons. The source for these add-ons is still available on Bitbucket.

Tour
header-translationsTitle=Doctype Add-on






Section
titleDynamic Value Handling

Although property values must not be dynamic, it seems that users just love to use them. There are use cases where this makes sense, but mostly the information architecture will get in trouble, once the whole set of projectdoc documents needs to be rebuild.

This version provides some tools to check the current state of dynamic values on your server. It also provides some configurations to handle the use of dynamic values in the future.

In case you need to stick with the old lenient model, set the checking to off. This approach is not recommended. You can use REST services to check which mode is most appropriate to your information architecture.

For more information, please refer to 

Static Document Link
documentDynamic Property Values


Section
titleCalculation Macro

Prior to this version there was only minor support to do some calculations. With this version there is the

Static Document Link
documentCalculation Macro
and the 
Static Document Link
documentCalculation Result Macro
. It allows to run calculations on double values and render the results.

Currently there is no support for integer values, therefore use cases that require "full precision" (for instance calculations with currencies) are currently not supported.

Please refer to

Static Document Link
documentCalculation Macro
for more information on how to use calculations in your Confluence instance using the projectdoc Toolbox.


Section
titleForm Identifiers

Due to issues where the form identifiers are not properly encoded, we decided to replace the dots as separators with underscores. Therefore the name/identifier of a form field, for instance projectdoc.doctype.common.name is now specified as projectdoc_doctype_common_name. This is true for all identifiers used in the wizard.

This will reduce the amount of failures when the forms are processed with code that does not properly encode these identifiers.

Code Block
languagetext
titleExample: Error Log from the Browser's Console
Uncaught DOMException: Failed to execute 'querySelector' on 'Element': 'label[for=projectdoc.doctype.common.name]' is not a valid selector.

More information on using dots with identifiers can be found in 

Static Document Link
documentIdentifiers with Dots
.

Due to this change all doctype add-ons are required to be updated for version 6.0 of the projectdoc Toolbox!




...