Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
Here is an example workbench definition from the Contacts app. This workbench operates on the
contacts workspace and displays contacts and folders.
Defines how users can view content in the workbench. The parent node for the specific content view definitions. It must contain at least one content view, see Content view definition.
optional, default is true
optional, default is AlwaysTrueDropConstraint
A drag-and-drop constraint class. By restricting the nodes that a user can move you can enforce a certain node hierarchy. For example, you might want to allow content to be moved under folders but not folders under content. If the class is not defined, the
Makes the workbench editable inline. You can double-click a cell to edit its value. Works only for columns which are also configured as editable.
Inline editing is available only in the tree view, not in list, thumbnail or search views.
Definining a default action will override inline editing. Double-clicking the cell with trigger the default action instead of inline edit mode.
A list of configured content tools. (A content tool must be configured with
$webResourceManager.requireResource("info.magnolia.sys.confluence.artifact-info-plugin:javadoc-resource-macro-resources") WorkbenchPresenteris implemented in a way that it automatically configures a "search box" if you have both list and search view defined.