Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Document Properties Marker
overridefalse
Short DescriptionRenders the list of child documents, matching the given filter criteria.
Doctypemacrohide
NameChild Documents Macro
Parent
Parent Property
property-nameName

Audience

Name List
doctyperole
render-no-hits-as-blanktrue
namesAuthor
propertyAudience


Type
Name List
doctypemacro-type
render-no-hits-as-blanktrue
propertyType

Subject
Name List
doctypesubject
propertySubject

Categories

Name List
doctypecategory
namesLink / Document
propertyCategories


Tags

Tag List
namesLink, Children
propertyTags


Iteration

Iteration
valueproduction

hide
Since3.2.3
Deprecatedhide
Removedhide
Sort Keyhide

...

Section
titleProperties
Section
titleDoctypes

The comma separated list of doctype identifiers.

Only child documents of the given doctypes are considered as match. If no doctype is specified, all doctypes are valid.

Section
titleMatcher

The parameter value is a constraint the documents need to match to not be filtered from the result set.

The syntax is different from those you specify in case you run a Lucene search. As in queries you check the property values of the child documents.

If the property name you need to match is a alphanumeric token, you do not need to encode it (e.g. Year=2019). If it has a space, used $[...] as delimiters for the property name. For instance $[Customer Reference]. This is similar to the encoding used for Lucene queries with the Display Table Macro. You may also use ${...}  or $<...> as delimiters. But there is no reason to do so since property names should not contain special characters. We recommend to use the square brackets ($[...]) since these are also used for Lucene queries of the property name contains a space (see Search Tips).

Values that have no spaces and are plain tokens need not to be encoded to compare with a property property value (e.g. $[Zip Code]=45672. In case there is a space, you can use quotes as in $[Customer Reference]="123 ABC".

You may also compare the property value of the document in the result set with a property value of the document the macro is part of: $[Customer Reference]=${Default Customer Reference}

You may combine your property constraints by the following Boolean operators.

OperatorDescription
&AND - both properties need to match
|OR - only one of the two properties need to match
!NOT - only true if the property does not match.

Use parentheses to group your expressions.

Example Box
titleExample Matcher Expression with !, |, and &
Code Block
languagetext
!($[Property A]="Value 1" | !$[Property B] = "Value 2") & $[Property C] = "Value 3"

Currently the projectdoc Toolbox does not support list searches or comparisons with greater than or less than. Only exact matches are supported.

Section
titleProperty Name

By default the name of the matching documents is rendered. The Property Name Parameter allows to select another property to be rendered for the link. It should be a unique property such as the Short Name or an Identifier.

...