The edit view displays one entity in a form, allowing the user to view or change the properties.
Functions of the edit view:
For more information on edit views see Documentation → The user interface → The Edit view.
To open the Edit Views view, navigate to Develop ➔ Edit Views.
Fields in the sidebar:
The edit view name is part of the URL for the edit view.
The URL scheme for the edit view is:
https://[instance name]/[app name]/#edit$[edit view name]
Accessing the search view is done by entering the above URL in your browser. Another way to access the edit view is by adding it to the menus or by connecting it with a search view.
The name of the entity.
The title for the edit view, as viewed by the user in the tab bar button when the entity is being added.
Usually the title defined as a concatenation of "New" and the entity name. No restrictions are imposed on the title as it can contain spaces or any other special characters.
Eg.: the entity "product" should have the title new "New Product"
The title for the edit view, as viewed by the user in the tab bar button when the entity is being edited.
Usually the title defined as a concatenation of the entity name and a descriptive property of the entity. The descriptive property can be injected as environment variable.
Eg.: the entity "product" should have the title edit "Product ${name}". This will display to the user a title that includes the name property value of the edited entity.
The title of the edit section.
The related print view for the edit view. It is used by the edit view to handle the print function.
This field is optional but omitting it will disable the print function.
It the print view is already defined it can be selected from the drop-down, if not it can be created by clicking the Navigate link.
The module to which the edit view is part of.
This field is optional.
The unique global identifier for the edit view.
This field is automatically generated by the Link system module. This field is optional but omitting it wil make the search view unsendable to another server.
Entity diagram:
Fields in the inputs table:
Tab entity diagram:
Fields in the tabs table:
Select the Tabs tab, click the Add button, and specify:
Click the navigate arrow next to the Search view field.
Create the search view for the related entity (representing the "Many" part of the relationship).
The search view requires a filter to relate the parent entity with the child entity. After configuring this filter on the search view, specify it in the Fetch tab.
Tab entity diagram:
Fields in the actions table:
Tab entity diagram:
The Edit View can be customised by setting the following properties.
The configuration tab is a JSON input in which you can enable or disable additional configuration options for the edit view.
{
"expanded": false,
"timestamp.visible": true,
"buttons.delete.visible": true,
"buttons.saveAsCopy.visible": true,
"options.visible": true,
"options.expanded": false
"options.sharing.visible": true,
"options.ownership.visible": true,
"options.actions.visible": true
}
The properties can be set individually, the properties not set will have their default values as above.
expandedfalsetimestamp.visibledate_created and date_updated fields of the current entity presented in the view.truebuttons.delete.visibletruebuttons.saveAsCopy.visibletrueoptions.visibletrueoptions.expandedfalseoptions.sharing.visibletrueoptions.ownership.visibletrueoptions.actions.visible