Download as PDF


The navigation through data objects in the work areas is generally divided up into the structure tree on the left, the object structure window above the object detail window and the path display. The three display options mentioned are not necessarily present in every work area and may be omitted depending on allocation.

The structure tree shows all objects in the form of a tree, which the logged-in user may work on within the respective area based on his group rights.

A tree is a special graph, and to put it simply, a hierarchically ordered set of objects which stem from a common root. Thus there is an object under which all other objects are located (the so-called systemroot object). The relationship between the objects can be pictured like that of related family members within a family tree. There are ancestors, descendants, parents, children and siblings.

The individual branches of the object tree can be expanded and collapsed. In doing so, the status of the individual branches is saved. If a branch expanded further is collapsed, then the expanded part becomes available again when the branch is reopened.

When loading a work area with a structure tree for the first time, the width adapts to the content of the structure tree. If the area should make working in the object detail window more difficult, then the frame between these two areas can be dragged with the mouse. Double clicking on the frame will instruct it to adapt to the width of the structure tree. If the frame is dragged to the left and to the edge of the browser window, then the Editor will offer to minimise this structure tree. If the structure tree is hidden, then a path display will be shown over the object detail window or over the object structure window. This path display represents the path to the document highlighted in the structure tree. Before the path display, the user will be given the option of showing the structure tree again.

In the path display, the user can navigate further through the data structure. When clicking on the path elements, the user is offered to select one of his child elements or to remove the clicked path element.

The object structure window above the data processing field is optional and is additionally configured as needed. It shows objects in a list and information can be added to it depending on column configuration. This representation is an alternative to the representation of objects in the structure tree. The objects listed in the object structure window are therefore child elements of an object in the structure tree.

When looking at the editor for the first time you will see that, unlike with most other information or content management systems, there are very few buttons and toolbars. The user interface is not cluttered, but streamlined and functional. In order to make this possible, makes intensive use of context menus as well as the dragging and dropping of objects.