Entity schemas define the structure, validation rules, and identifiable information of data. By default, all data flowing through your integrations are assigned to the default entity type. In this case, no structure, validation, or identifiable fields are present. Your Alumio environment will come with a set of standard entity schemas which offer pre-set structures and validation while also allowing you to create your own.
Entity schemas can be created and maintained by navigating to Settings -> Entity schemas.
Creating and maintaining entity schemas
Possible configuration fields:
Name - A name describing the type of entity, i.e. ERP Product
Identifier - A unique identifier for this entity type (this field is automatically generated based on the name).
Description - Detailed description for the entity type.
Disabled - A flag that indicates whether the entity type is disabled. Disabled entity types disable any integration where this entity type is being used.
Schema - The schema defining the structure of the data as well as the applicable validation rules.
Identifier path - The fields which make up the entity identifier. This is reflected within the tasks and storage.
Link - The link in which the documentation of the schema can be found.
Automatically validate incoming data
Within Alumio you can set up a JSON schema(full documentation available here)to automate the validation of incoming data. Entity types allow you to set up a predefined schema that specifies the required structure of the data as well as data types and other validation rules such as the minimum length, the maximum value, or legitimate values.
On the example image above, the following schema has been defined: