> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/june5-3.7/en/webanwendung/sichten-editor.md). # View Editor The Views Editor allows you to freely design additional views. It is accessible via the Views Editor menu item. The permission to create a custom view is granted in User Management via the corresponding functional right. {% hint style="info" %} In Multi-Tenant Mode, each newly configured view is assigned to exactly one tenant and cannot be moved or copied from tenant to tenant. {% endhint %} ## The Interface and Configuration The Views Editor consists of two halves (Split Screen). The left and the right half. On the left half is the object selection, which can be used when creating a new view. From here, desired objects are transferred to the right half, where the display of the new view subsequently takes place. In the middle of both halves is the vertical dividing line, with which the width of both halves can be adjusted as desired. To the left of the dividing line are two buttons. The upper button transfers the objects marked by checkbox to the right half. The lower button, on the other hand, transfers all currently displayed objects except groups to the right half. The toolbar positioned at the very top contains two buttons: * View Selection (offers the selection of a new view and additionally a selection of already generated views). This control also contains the delete button for the already generated views. * Save (saves the created view) ### Left Half (Object Selection) As already mentioned above, this half contains the object selection. The object list has all important controls such as in [List View](/june5-3.7/en/webanwendung/listenansicht.md) (Pagination, Sorting, Search, Breadcrumb Navigation, Object Filter, etc.). Here the object list can be displayed both flat and hierarchically. From here, objects can be placed in a new view (right half), either individually (via Drag & Drop) or multiple (via Checkbox). ### Right Half (View) Here, the new view is created at the end. This area also has all important controls for the object list (Pagination, Sorting, Search, Breadcrumb Navigation, etc.). The object list here can only be displayed hierarchically. The corresponding navigation to the desired hierarchy level then takes place as usual via the breadcrumb navigation. Furthermore, this area contains buttons for renaming the view, for discarding changes, and for defining new groups. The input fields for renaming the view and for defining a new group can each be expanded and collapsed using the associated button. Newly created groups or inserted objects are marked in green and always appear in this object list at the current hierarchy level. #### Group Handling * Groups can be structured in the editor. * A group can be moved into another group. * Groups can be deleted. * Groups can be renamed. #### Controls on List Items * Groups contain the delete, rename, and move group buttons. The move button is not selectable for newly created groups. * Objects (such as measured values, reports, or custom objects) contain only the delete button. All these buttons are found under the button with three dots. #### Move Group Moving a group is done via the so-called Move Group button, which is hidden under the button with three dots. When this button is selected, a modal window is opened. At the very top of this window is a breadcrumb navigation and directly below it a hierarchical view of the current view. The explicit selection of the new parent group is done by selecting one of the circular checkboxes located to the left of the desired parent group. The selection of the new parent group also occurs (automatically) when a group in the object list or breadcrumb navigation is clicked. #### Sorting Objects Sorting is done in two ways. Via Drag & Drop or using arrow keys. **Drag & Drop** The object is marked with the (left) mouse button held down and then dragged to the desired position and released. **Arrow Keys** This is done via the so-called Re-sort button, which is hidden behind the button with three dots at each object. When this button is selected, four arrow buttons appear at the bottom of the screen (where pagination was previously). Using these four buttons, the desired object in the current object list can be moved to the first or last position, as well as step by step one position up or down. All of this must be confirmed at the end with the OK button. ## The Role of the Standard View (SV) The Standard View is retained and is always created when synchronizing with the data source, just as before. The Standard View is as usual available as standard for every user. In the Views Editor, the Standard View serves as a source for additional freely configurable views. The Standard View itself, however, is not editable. The visibility of objects in the Standard View is controlled by the rights in the object model. That is, a user can only configure a new view for objects that are visible to them. ### What are the effects of changing an object Changing any object has an effect on all views in which that changed object is contained. It does not matter whether this object was changed in the Standard View or in one of the custom views. Changes can occur, for example, through synchronizing data sources or by renaming a custom object as well as changing the number of measured values in a chart object. There is always a real object that is linked as a reference in every view. ## Behavior in the Views View If no start view is configured, the Views view starts with the Standard View. The freely configured views are parallel to the Standard View accessible/selectable. Just like the Standard View, all freely configured views can be displayed flat or hierarchically. ### Storage Handling of Custom Objects When, in the Views view, a custom object is created/saved under a newly configured view, this can occur differently depending on the current list type (flat or hierarchical): #### Flat List Here the custom object is created in the currently selected view as a direct child object of the root directory. #### Hierarchical List Here the custom object is created in the currently selected view as a direct child object of the currently open group. For both list types, the created object is also created in the Standard View as usual. ## Configuration of a Start View From already created views, one can be set as the start view. This is, like the start object, set under User Management. Furthermore, it can be configured here whether the selected start view should start as a tree when accessed (in Views view). After logging in, the Views view now starts with the previously set view. By default, the Standard View is set as the start view. {% hint style="info" %} The configured start view becomes effective only after a new login. {% endhint %} ## Effect on the Start Object The start object and the start view are dependent on each other. Since each available view can contain different objects, a start view must first be selected so that one of the objects it contains can be selected as the start object. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.videc.de/june5-3.7/en/webanwendung/sichten-editor.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.