Versions Compared

Key

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

...

Document Properties Marker
doctypetopic
overridefalse


Short DescriptionConfiguration to control how the projectdoc Toolbox handles property values with dynamic content.
NameDynamic Property Value Handlinghide
Short Namehide
Parent
Parent Property
property-nameName
hide
Audience

Name List
doctyperole
render-no-hits-as-blanktrue
render-list-as-comma-separated-valuestrue
namesConfluence Administrator, Documentation Architect, Documentation Gardener
property-restrict-value-rangetrue
propertyAudience


Subject
Name List
doctypesubject
propertySubject

Categories
Name List
doctypecategory
property-restrict-value-rangetrue
propertyCategories

Tags
Tag List
propertyTags

Flagshide
Iteration

Iteration
valueproduction

hide
Type

Name List
doctypetopic-type
render-no-hits-as-blanktrue
namesReference
property-restrict-value-rangetrue
propertyType


Level of Experience

Name List
doctypeexperience-level
render-no-hits-as-blanktrue
namesNovice
propertyLevel of Experience


Expected Duration
Sponsors
Name List
doctypestakeholder,organization,person,role
render-no-hits-as-blanktrue
propertySponsors

Since6.0
Sort Key001-00200hide



Section
show-titlefalse
titleDescription

The use of dynamic content for property values is typically a problem. The projectdoc Toolbox provides since version 6.0 tools to help responsible stakeholders to manage the use of dynamic content in their information architecture.

This topic shows the configuration options and provides links to further information.

...

Section
titleConfiguration Options

Via the graphical user interface administrators have the following options to control the handling of dynamic property values in their Confluence instance.

The configuration options on the administration screen within Confluence for controlling the handling of Dynamic Property ValuesImage Modified

After changing the mode a refresh of the site is required.

Section
titleMode

The mode controls the general handling of values.

The modes lenient and strict are recommended to be used as runtime modes.

The mode allow is for backward compatibility only. It puts no restriction to the use of dynamic values. It is recommended to check the spaces with projectdoc documents with the health services to learn, which mode may be most appropriate for the current use of properties in projectdoc documents.

The modes explicit and block are typically only used to find possible issues using the health service.

Transclusion
documentDynamic Property Values
idstable-of-modes


Table: Modes provided on

Static Document Link
documentDynamic Property Values


Section
titleSkip Default Macros

The projectdoc Toolbox defines macros that must be treated as dynamic if used as property values in projectdoc documents.

In case you do not agree with this definition, you may switch off this configuration (setting a check to Skip Default Macros) and do the definition of dynamic macros completely on your own.

It is recommended to keep this checkbox unchecked and therefore take advantage of the default configuration.


Section
titleDynamic Macros

List additional macros users of Confluence are using, especially as values of document properties.

The list contains the identifier of the macros considered to be dynamic, separated by comma. These macro identifiers can be found in the storage format of the macro definition and maybe in the documentation of the macro.

When projectdoc encounters such a macro as value of a property, then the property value is treated as a dynamic value that requires special handling dependent on the selected

In-Document Link
anchorMode
.


...