...

Modeling Forms for Metadata

 cannot distinguish object type and SOT

...

In the Properties area, you can give groups a unique technical name for identification key. This key technical name is required in order to display a label for the Group in your form. Customize the labels via Localization. If not specified in the corresponding localization configuration, the identification key will technical name will be displayed in the metadata form.

...

• For a single property field, you can tick or untick the checkbox Read-only in order to define the behavior in the client. For a string property, you can modify the number of Lines that will be provided for the property field in the client.
  Under Schema you can see the attributes of the schema property definition for the selected property.
• For a table property, you get the Read-only checkbox together with the Schema attributes of the property definition, too. Additionally, an overview of the available columns is provided. They are named with their identification key and technical name and their type (string etc.). By clicking one of them, you can define for the individual column the number of Lines for each entry and to be Read-only or not. By drag and drop, you can change the order of the colums or move them between Colums used and Columns not used. Thus, you can include or exclude columns from the metadata form.
• For a Group, you can select either Row or Column as Layout for the arrangement of the included property fields. Except for the Main Area, you can define a unique technical name for  identification key for of the Group. This key technical name is required in order to display a label for the Group in your form. Customize the labels via Localization.
• For a GroupStack, there is no second information block displayed.

...

...