Description
Within Build.One Content Types will be used in many different ways to integrate different types without any coding or database schema changes. Not every use case for content types needs every attribute.
Examples:
- Control SwatImage: Define different image types for different screens where images are needed
- Control SwatText: Define different text types for different screens where text is needed
- Control TreeGrid: Define different position types
Attributes
Types | Description | Example | Mandatory for types: |
Flag | If it is a System-Type it will be provided by Build.One. User-Types are client specific. | S=System
U=User | all |
Internal | |||
Misc | |||
ParentTableID | |||
Description | description of the type | Image type for the client logo | all |
Key | Unique key for different types, group it via "." (e.g. all text types should start with "txt.")
This will be used e.g. in a TreeGrid to define, which content types should be displayed there (e.g. all which start with img.clt.*) | img.clt.logo | all |
TargetTableID | |||
Type sort | If there are more than one type within a group (e.g. text-types txt.*) you can sort them with this attribute | 1 | all |
Transform type | |||
Valid parents | |||
Can make copy | |||
Creatable | |||
Deletable | |||
Must path parents | |||
Integration Name | |||
Parent Group | |||
Data Source | |||
Data Source Options | |||
akUiOptions |
How to use it
- Open desktop “Types”
- Change a content type through inline editing and saving it via the panel header menu
- Add a new content type with the FAB
Back to 
Documentation
Back to Home Page