Should be yet another property but cannot be deleted. In first iteration it's shown and next when we introduce 'advanced mode' it's shown only in advanced mode.

The link between a join key property and its relation definition must be updated when changes to the joining property occur or it must be based on a property that does not change. Either way, there should not be a situation a join key property is orphaned of its relation.

change generation templates per entity instead of using globally the ones in settings

add order property on entity properties (commonly used by ui templates)

'small' must be varchar with length 40 and not char with length 100
'medium' is varchar with length 255
'huge' is varchar with very large length (10000)

No matter your input the relation's join key name will not be considered actually.

Sometimes the toolbar contains the buttons that are relevant for no-model state. Reloading again fixes the issue.

relation join keys (key and the associated fk) must be part ofo a relation definition and managed atomically. (creating a relation creates a fk in the target entity, deleting a relation deletes the associated fk in the target entity)

pre-select input filed text fro property label

validation of order fireld in prop editor should not require additional click

order of columns passed to templates must be asc (0->N)

introduce expert/simple mode and global settings

property name and column should be sensitive to property label changes and comply

It should be possible to get more details for a relationship without moving to edit mode

project and package name validation should not allow invalid names

A power user should be allowed full control on the model. The delete buttons that are normally disabled to prevent accidental delete and inconsistency should therefore be enabled in expert mode.

more property details in expert mode in property list view

The option will set the package and project name strings to global settings so that next time a build dialog is opened, it will have them automatically populated already. Would be useful for frequent builds on the same project

Call the publish project after the generation process

After change of the Name of the Business Object this to be applied to the configurations artefact names

many-to-many relation should create a new (join) entity that is marked as special and visible only in expert mode. in expert mode one should be able to also add properties to it but in simple mode this entity is managed transparently.

Show a message after the project is built and published

Handling and/or validating the Name/Label in properties defintions

auto-order properties in new entity template

sql type validation/suggestions in expert mode edit of prop type

A join key property should provide information for which relation it has been created and ideally be able to jump to the relation for details.

Opening settings while in edit mode will reroute the user to details. The settings should be an 'overlay' and not affect the views route.

Currently settings live within a user session. They should persist across working session too.

relations are not harmonized (what is outbound and what is inbound)

Properties should contain a minimal set of common characteristics (id, label, name,..) and a set of characteristics that are dynamically provisioned by the selected templates for the entity.
The templates service should therefore report the name, label and variable properties for each template. The variable property should be characterized by name, label and type constraints.

Collectively, there should be enough data to represent it in the property detail and editor homogeneously with the standard property characteristics. This includes validation rules. For example if the property characteristic is a positive integer, such as order, it should supply this rule in a consumable way to the editor to set the corresponding HTML5 attributes on an input element. If the property values are discrete with more than two alternatives, it should provide the options in a way suitable for rendering as type-ahead combobox.

Overall, the rendering of property characteristics should detach from completely fixed set for concrete templates and become an algorithm based on a contract defined by the requirements above that can be fed properties to render and persist dynamically.

Notifications bar should appear in top left, half page width

property order should apply to database table definition

The editor should be flexible enough to provide for changing also the source key and the model should account for this possibility

Default of the Build Apps Dialog to be UI as a full-stack application