Versions Compared

Key

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

...

Section
titleSpace Property Constraints

Currently there is only one space property to put constraints on the result set for names to be presented for Autocompleteprojectdoc.autocomplete.activeConstraint.

This property specifies a constraint that must be met be names in the result set in addition to constraints defined by macro parameters. The property can be used to define that only names from documents that are in Iteration Released, Production, and Deprecated should be presented for selection. Please refer to projectdoc.autocomplete.activeConstraint for an example.

projectdoc-box-note
titleExplaining the Where Clause

The Where clause shown above shows every doctype besides Event and todo only as an option in an autocomplete if it is in Iteration Released, Production, or Deprecated. In case of an Event or Todo, the Iteration needs to be in Facade, Filled, Focused, Finished, or Released.

Code Block
(
  ($<Iteration>~(Released,Production,Deprecated) NOT $<Doctype>~(event,todo))
  OR 
  ($<Doctype>~(event,todo) AND $<Iteration>~(Facade,Filled,Focused,Finished,Released))
)

For more information on queries with the projectdoc Toolbox, please refer to Search Tips.




projectdoc-section
titleCaveats

Some tips on using Autocomplete that may save some time on occasion.

Section
titleLiterally

Names are meant literally. In case a name of a document is changed, the names in macro parameter values are not changed. Neither in the Names parameter, nor in the Where or Sort By parameter.

This is by design. More information on this topic is found in the tip Changing Names.


Section
titleDoctypes missing

In case the Doctype parameter does not show all expected values, the doctype cache may be corrupt. In this case a user with appropriate access privileges needs to refresh the doctype cache.

For more information on refreshing caches, please refer to Cache Refresh Actions.


Section
titleParameters Coverage

Currently not all parameters of macros are fully covered by the Autocomplete Feature. While all macros support Names, Document, and Doctype Autocomplete, only one macro supports Document Property Name Autocomplete. Further Autocomplete support will be available in future versions of the projectdoc Toolbox.

The lack of support for a number of parameters may be not intuitive for some users. In case this troubles users, the Autocomplete Feature may be turned off by the administrators.

See Autocomplete for details on how to do this.


Section
titleMacro Parameter Panel

The support for setting macro parameters can be extended to the macro parameter panel. Confluence provides such a feature for the Status Macro, the projectdoc Toolbox for the Iteration Macro.

Macro parameters for the Names parameter will be shown in a selection box. Currently the focus handling has some issues. Therefore this feature is turned off by default. Administrators may turn it on in case it supports the productivity of their users more than the quirky focus handling offends them.

See Autocomplete for details on how to do this.


Section
titleTagging everywhere

In previous version of the projectdoc Toolbox tagging, the use of new names to support ad-hoc taxonomies, has been supported by all Names parameters. In the latest release of the projectdoc Toolbox and the related doctype add-ons, this support has been limited. Audience properties the roles, for Categories parameters the categories, and all Types properties referring to doctype types need to be defined in advance. We call this using prepared taxonomies. Only Tags properties are supporting ad-hoc taxonomies per default.

In order to go to the old state, there is a feature to support ad-hoc taxonomies for all Names parameters. See Autocomplete for details on how to do this.


...