Page History
...
Note |
---|
We highly recommend using the same |
...
Browser subapp
A JCR content connector definition introduces properties that identify a JCR workspace as a data source. It also defines the node types to operate on.
...
| required List of node types the content connector operates on. For example, the connector in the Contacts app displays contacts and folders. |
| required Arbitrary node name such as |
| required Node type the connector operates on. These are Magnolia or JCR node types such as |
| optional , default is none CSS class name of the icon displayed on the workbench. See the default icons that ship with Magnolia or create your own. |
| optional Specifies whether to include only the exact node type and ignore subtypes. |
| optional Specifies whether to display the current node in list view. Use this property to, for example, exclude folders. |
| required A workspace in the |
| optional Default sort order for the content items in list views. The value is the name of the property you want to sort by, such as |
| optional, default is Displays also the JCR properties of the node when set to |
| optional , default is Displays also nodes used by the system such as nodes internal to the operations of the JCR implementation. Set to |
| optional , default is Path configured as the root of the workspace. Only content below the path is operated on. |
...
Detail subapp
The connect definition for a detail subapp is much simpler. You only need to define the workspace.
...