Data Model & Schema¶
Cellmobs offers a highly flexible core data model, consisting of commonly used entities such as Identities (Users), Organizations, Products, Content (Files), and more. This flexibility allows users to build a wide range of applications tailored to their specific requirements.
| ||Defines the role of an |
| ||The properties and value of an API Key|
| ||A Calendar Event|
| ||A shopping cart associated with an |
| ||A syndication channel configuration|
| ||A file of a certain content type|
| ||The terms of an agreement between two or more parties|
| ||A |
| ||An aggregation feed configuration|
| ||Payment information, Credit Card or Bank Account|
| ||Credentials for an API Integration|
| ||A user, person, individual|
| ||Rendition settings for a |
| ||An email, notification, or chat message|
| ||An invitation for an |
| ||A business lead or contact request|
| ||A entry in the revenue |
| ||A report generated from a |
| ||A revenue and cost ledger of an |
| ||A geo location of a certain LocationType: RESIDENCE, OFFICE, etc.|
| ||A custom data model|
| ||The credential for and OAuth API Integration|
| ||An order with a |
| ||An organization or group of some kind|
| ||The configuration and credentials for a payment gateway|
| ||A payment transaction|
| ||A poll with one or more questions|
| ||A product, a good or service|
| ||A project, that contains multiple |
| ||A product promotion that can be applied to an |
| ||A entity rating of a certain type e.g. |
| ||Defines an arbitrary relationship between two entities|
| ||Defines the field value requirements for entities and validation workflow|
| ||A |
| ||Defines what triggers an |
| ||A reward for |
| ||A subscription plan consisting of one or more |
| ||A subscription of an |
| ||A tag (category or label) associated with an entity|
| ||Defines a tax or fee aassociated with a |
| ||A tenant also knows as a Cellmobs App|
| ||A configured value of a Vocabulary|
| ||Defines the content of a web page|
| ||A email, web, or report template|
| ||Defines task aka story, ticket typically associated with a |
The core data model can be extended in two ways: Custom Field Templates and custom Models.
Custom Field Templates¶
Custom Field Templates provide a convenient way to extend existing model classes with additional fields. Users can define sets of fields as templates that can be attached to new or modified entities. This allows users to add custom attributes to entities, enabling them to capture and store additional information specific to their application's requirements. Custom Field Templates make it easy to expand the core data model without the need for complex code modifications or database schema changes.
Click here to learn how to configure customer field templates.
In addition to extending the core data model, Cellmobs supports Entity Requirements, a feature designed to validate entity field values based on configurable business rules in support of certain use cases and workflows.
Entity Requirements help ensure data consistency and integrity by enforcing specific conditions and constraints on entity attributes. This allows users to maintain high-quality data in their applications, ultimately improving the overall user experience and reliability of the system.
Click here to learn how to configure entity requirements.
For more advanced use cases, Cellmobs allows users to create entirely custom Models. This feature provides even greater flexibility, enabling users to define their own entity types with custom attributes, relationships, and behavior. Custom Models can be used alongside the core data model to build sophisticated applications that cater to unique business requirements.
Custom Models are still in the experimental stage and will be rolled out later this year.