...
| Advanced Tables - Table Plus |
|---|
| highlightColor | @default |
|---|
| multiple | false |
|---|
| enableHeadingAttributes | false |
|---|
| enableSorting | false |
|---|
| enableHighlighting | false |
|---|
|
Parameter | Description | Parameter type | Data type | endpointPrefix
| required The name of an endpoint prefix as configured in YAML . Also can be a real workspace name. | path
| String
| q
| optional A search phrase (full-text search) | query
| String
| orderBy
| optional The properties by which to order the nodes. Example: mgnl:lastModified desc,title asc* | query
| String
| offset | optional, default is 0 The start position in a result list (for pagination) | query | Integer | limit
| optional, default: as set in YAML configuration The number of nodes displayed in a page query. Used together with offset for pagination. | query
| Integer
| <filter> | optional Use a property as a filter; it must match exactly. Example: author=Magnolia%20Travels* There are multiple filter options to filter for a property of the node, for node names, for nodes which must be ancestors of a given path, you can combine filters with AND operator. See filter options. |
|
|
|
*) Note that special characters such as a space ( ) must be encoded when sent in an HTTP request. When using tools to generate a REST request, this may happen automatically. With simple cURL you have to encode it manually or with an additional tool. Example: orderBy=title%20asc
...
queryNodes provides a filtering mechanism with the following features. Filters are added as request parameters.
Property filter
Filter for a property of the node. Example: author=Magnolia%20Travels*
| Anchor |
|---|
| example-queryNodes |
|---|
| example-queryNodes |
|---|
|
Examples
...