Page History
...
To retrieve a value reference called @Project Lead@
, you would use the following add the {get-metadata}
macro to content using the macro editor to add the metadata name (note: no @
symbols).
A simple way to display the value is to add the macro to a table cell.
On the content, this retrieves and displays the current value of the metadata.
In code notation:
Code Block | ||||
---|---|---|---|---|
| ||||
{get-metadata:name=Project Lead} |
Metadata values created with the {set-metadata} macro are only indexed by Confluence and appear in the Confluence search if the Comala Metadata app is installed.
Metadata retrieval logic
The following may cause problems when trying to retrieve a metadata value using the get-metadata macro.
For example
- in Comala Document Management versions prior to v6.18.8 using a
get-metadata
macro to define a page property value where the metadata being retrieved is the value of anotherget-metadata
macro
The retrieval logic of the get-metadata
macro may also have problems returning a value if there is any coincidence (or overlap) in a metadata name and another metadata or property name. To avoid any problem simply try to ensure the use of unique names for each of your metadata names.
Suppose duplication of a value reference name occurs, for example, a page property and metadata set with the Comala set-metadata macro. In that case, the get-metadata
macro will resolve the value in the following priority.
- Confluence page properties macro
- Comala Metadata which includes workflow parameters with
edit=true
that have been saved and metadata set using Comala Document Managementset-metadata
macro - Communardo Metadata
- Workflow parameters saved at the space level - without
edit=true
- Page references
- Suppliers (ServiceRocket, Workflows, Metadata)
All examples
Content by Label | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...