Improvements, including Support for List Values in Matcher, and fixes.
Today we released version 6.2.5 of the projectdoc Toolbox on the Atlassian Marketplace!
The projectdoc Toolbox is an add-on for Confluence supporting agile software development teams to collaborate on process, project, system, and product documentation.
If you want to learn more about the projectdoc Toolbox and how it helps to create good project documentation, please refer to the introduction video!
The following image is a link to a video on YouTube. When you click the link your browser will serve a page from youtube.com.
Very interesting, but way too fast?
Step through at your own pace with with our Prezi Presentation (external link to prezi.com )!
In the Online Manual you’ll find additional video material that introduces you in the concepts of the projectdoc Toolbox.
Refer to use cases and show cases for information on how to use the projectdoc Toolbox.
New and Noteworthy
Support List of Values for Matcher
The Matcher Parameter, for instance of the Name List Macro, now supports list of values.
$[Customer Reference]=${Default Customer Reference}If Customer Reference and Default Customer Reference both resolve to lists of values, then each value of each set is compared. If one tuple matches, the whole expression is resolved as a match.
See
List of Changes
The following changes are part of version 6.2.5 of the projectdoc Toolbox for Confluence.
| Key | Summary | T | P | Description |
|---|---|---|---|---|
| PDAC-1772 | Support List of Property Values for Matcher |
|
|
The matcher (for instance with the Name List Macro) can only be applied to single value properties (like Value A). We should support multi-value properties (like Value A, Value B, Value C). A list of literal values is not covered by this improvement. |
| PDAC-1776 | Level Issue on Confluence 8.5 |
|
|
When calculating the level, with version 8.5.0 of Confluence the calculation of a rendered property requires a normalization. |
| PDAC-1773 | Parse Error in Matcher |
|
|
If there is a parse error in the Matcher parameter, the autocompletion returns with an HTTP 400 that is not successfully processed on the client side. Therefore the progress indicator will never stop. |
| PDAC-1770 | Tour Macro fails with empty first Column |
|
|
If the first column of the table inside a Tour Macro contains empty cells, the referenced sections will not be rendered. If the cells contain non-empty values or it contains the references, everything works as expected. Also property values or text values are always correctly rendered. |
| PDAC-1765 | Encoding Issue with Space Properties |
|
|
The value of space properties when used for placeholder replacement in the context of the space console are not properly encoded. The normalized value, a text value, is fed as an original value into the space property. Original values are HTML values and are required to be encoded. |
| PDAC-1767 | Do not render null values |
|
|
When rendering properties in a template, a value of 'null' must be rendered as the empty string, not as "null". |
| PDAC-1766 | Format Issue with Tour-by-Property |
|
|
The Tour-by-Property Macro renders a box without proper formatting. Only the body of the box macro is rendered. |
| PDAC-1777 | CSS for Heading Doctype |
|
|
When rendering the doctype in a table (for instance Display Table), the column heading label is rendered with a box. The heading should have not that special formatting. |
| PDAC-1775 | Artificial Properties for External Confluence URLs and wrapped Text URLs |
|
|
Artificial properties (link label and link URL) should be generated for Confluence URLs that point to external resources and for URLs in plain text that are wrapped in HTML elements (such as span or b). To have the new artificial properties generated, a refresh on the projectdoc database tables is required. |
| PDAC-1774 | Support JSON Responses in Web API |
|
|
For error conditions the Web API does not strictly adopt the returned value to be in JSON format. In some cases the response is rendered in XML. All calls need to support JSON requests. |