Here are two examples of deep links on the right side of a predicate (or right-side deep links for short)

The first constraint selects on all documents whose Type property is equal to this document's referenced Service's Type. We expect the value of the Type properties to be single values. Also the Service property is expected to contain no or only one reference to a service document.

$<Type>=[${Service->Type}]

Here is a similar constraint, but this time the property may contain multiple services.

$<Type>~(${Services->Type})

In this case the type must match at least one Type value of the referenced services.

$<Type>=[${Services->Type}]

Type="A, B"

Deep links on the left side (or left-side deep links) of a predicate reference the matching document.

The following predicate selects on documents who have a Type whose Tags match those of the current document.

$<Type->Tags>~(${Tags})

Again a similar constraint using lists and therefore using the list operator.

$<Categories->Tags>~(${Tags})

Materialization has three forms:

Adding a document property control is typically straight forward. Usually the mat control is provided in a template. If you place it in a document instance, then only the property of this instance is materialized.

Specifying the materialization as a space property automatically materializes the property for the referenced doctype. This only takes effect on document instances that are saved after this space property has been specified. All existing documents need to be reindexed.

The last option is simply a way to move the materialization directive from the document control to the doctype descriptor. If a user removes the mat control from a document, the property is no longer materialized for this particular document instance. The problem is that a type specific information is stored with every single instance of that type. While using the doctype descriptor to define materializations is a proper approach, teams deciding to not use doctype descriptors should use the other two approaches. Using space properties is probably easier for teams using doctypes defined by third parties. It is also less error prone to deletion of controls on document instances. But this is a problem inherent to all Confluence pages since there is no connection between the blueprint and the document after the creation process. Having the control in a template is probably more declarative and easier for teams using their templates in different Confluence environments.

Left- and rightside deep links can be combined in queries.

$<Categories->Tags>~(${Categories->Tags})

But remember to materialize the deep link for the left side queries.