You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Controls whether a line in a document properties marker macro is actually a property.
In document property marker macros users may want to have information in the table, but do not treat those values as actual document properties.
These "no-property properties" are not rendered when other properties are rendered. They are not indexed with Lucene and are not stored in the AO. In fact these properties do not have a cached rendered representation and do not have a normalized representation of any kind. So what you can do with these properties is simply use them to render in the properties table and to access the rendered HTML fragment with display macros, like the Display Document Property Macro or the Display Table Macro. The advantage is that properties marked with no-property can actually have dynamic values.
No-Index and No-Render
The no-property control makes sure that the property is not indexed (as with noindex) and not stored in the render cache (as with no-render-cache). In addition to that it does not provide normalized values. Normalized values are used with Lucene and when specifying queries (for instance Display Table Macro). Both it not possible with no-properties.
The use case for no-properties is the use of a rendered value. In an information architecture some dynamic listings may be placed in the table on top of a page. This is where the properties are specified in a table within the body of the Document Properties Marker Macro. Dynamic values are in many cases a very bad idea, but in some a proper solution. With no-properties in the properties table there is typically no problem with recursion.
