Bugfix release for issues regarding Autocomplete with the Name List Macro.
Today we released version 6.0.4 of the projectdoc Toolbox on the Atlassian Marketplace!
This is release provides a couple of fixes and improvements.
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
Names List and Autocomplete
The Name List Macro allows to run Autocomplete to support authors selecting proper names.
The Where parameter of the macro is applied to the Autocomplete, so authors cannot select invalid values. The new mechanism on filtering on the result using the Matcher parameter was not taken into account for Autocomplete. This version fixes that with
The Where parameter also has always been applied if specified. With this version (see
List of Changes
The following changes are part of version 6.0.4 of the projectdoc Toolbox for Confluence.
| Key | Summary | T | P | Description |
|---|---|---|---|---|
| PDAC-1723 | Name List Reference Issue |
|
|
When rendering a reference to a document with restricted privileges the Name List Macro must not render a proper link. |
| PDAC-1721 | Property Position Issue |
|
|
The position values in the AO table for properties are not updated properly. |
| PDAC-1712 | Property Matcher in Autocomplete |
|
|
For the Name List Macro the Where Parameter is taken into account for filtering on the Autocomplete function. When the user is specifying a property matcher, this is not the case. Autocomplete should only show those values that are allowed by the filter on the property values. |
| PDAC-1722 | Max Result Size Issue with Web API |
|
|
When running queries with a Max Result Size with the Web API, the result is not pruned. |
| PDAC-1720 | Page Creation Issue |
|
|
When storing a page programatically, for instance via the Web API, there is an error in the logs that states that the update process did not finish successfully. |
| PDAC-1718 | Blueprint Creation Issue with Confluence 8 |
|
|
There is a naming issue with the blueprint wizard handling that prevents the creation of certain macros. This is only an issue with Confluence 8 since it enforces modules. |
| PDAC-1713 | Where Clause Restriction |
|
|
For the Name List Macro the restriction of the Where parameter should only be applied to the Autocompletion filtering, if the Restriction parameter is set. Currently it is always applied. |
| PDAC-1719 | Use Spring Config instead of XML Config |
|
|
Use Spring Config as injection framework. |
| PDAC-1717 | Horizontal Tables for Property Marker |
|
|
Allow to render properties no only in tables and definition lists, but also in horizontal tables. |
| PDAC-1716 | In-Document Link for Blog Posts |
|
|
The In-Document Link Macro currently only works on pages, but not on blog posts. Blog posts should be supported, too. |
| PDAC-1715 | Default Value for Unset Dynamic Value Mode |
|
|
Users should be able to set a system property to control the default behavior for dynamic values in the case where no property has been set. Per default this value is 'allow', so that users get no constraints. Some users may prefer to start with 'lenient' or another mode. With de.smartics.projectdoc.dynamicValue.mode.initDefault set as a System Property, users may now set the default. In case a default value is set, but not understood (misspelled), the default will be 'lenient', not 'allow'. |
| PDAC-1714 | Sort Specification for Table Merger |
|
|
The Table Merger Macro does only allow to sort by one column and only sorts ascending. We need to support the default sort specification so that users may sort by multiple columns and also allow descending sort order. |