Before diving into entities, it's important to understand that in Slate, a record can have a one-to-many relationship with other records, such as test scores and relationship records. A common one-to-many relationship in Slate is a prospective student having multiple school records representing their academic history.
So what are Entities? Entities are new, custom objects/scopes exclusive to your database. A record can have a one-to-many relationship with an Entity; moreover, an Entity can belong to a person record, application record, or dataset record. Example entities include scholarships, class schedules, and more.
Entities can be used to gather and display data in the following Page Construction-scoped forms:
- Person Page (to be viewed on custom person tabs)
- Application Page (for custom application tabs, as well as pages within the Slate-hosted application).
Custom Entity Examples
An application can have multiple scholarships. In this case, a "Scholarships" Entity can be created with corresponding scholarship-scoped fields:
A person can have multiple courses. In this case, a "Class Schedule" Entity can be created with corresponding class-scoped fields.
Entities require the following configurations:
- Create the object (entity)
- Create entity-scoped fields that will be associated with the entity.
- Create an entity widget form to collect data associated with the entity
- Embed the entity widget form. The widget form can be embedded in Slate forms such as a custom tab or inside of a Slate application.