Enhancement
Critical
Major
Detail
Detail
Creating application views is currently done in a what-you-see-is-what-you-get mode. I.e. one creates a view and sees this view. To edit the parameters of the view, you have to see the view to be able to edit the configuration there.
This procedure is for many cases a prima solution, because one does not have to accomplish the abstraction achievement to find the configuration place in a large configuration tree, at which a completely certain property can adjust/change. Instead one can navigate to the problematic place in the application and let there the partial configuration be indicated. However, this approach reaches its limits if one has made such a mistake that prevents a certain view from being displayed at all. In this case the only possibility so far is to export the layout to the development environment and edit the XML there.
This can easily happen if you make a mistake in an executability rule that causes a button not to be displayed at all/anymore.
Improvement
Layout editor view in the development area, where you can view/edit/create the configuration of all layouts of the application without having to display the corresponding parent view at all (or having to switch the application to design mode).
Test
Navigate to the Administration > Development > Layout Editor view and edit and save a legacy and template layout.