Data Model Concepts
A Lowgile data model defines how your application stores, structures, connects, and accesses data across screens, workflows, and processes.
At a high level, the data model consists of three core components:
- Server Data Store: The connection layer between the application and the underlying database. It defines where data is physically stored and how it can be accessed or queried.
- Static Entities: Lookup tables that store reusable reference data, such as currencies, cost centers, countries, or externally managed lookup datasets.
- Transactional Entities: Data structures that capture business transactions, such as purchase requests, purchase request items, quotations, and quotation items.
Together, these components form a cohesive data layer that supports both application logic and workflow execution.
Entities in the data model
Section titled “Entities in the data model”Entities are the primary data objects used by screens, workflows, and services.
They define how application data is structured and how relationships between data are represented in Lowgile.
Entity Types
Section titled “Entity Types”Lowgile provides two primary entity types:
How entities are used
Section titled “How entities are used”Entities are used throughout the application runtime. They:
- Store and structure application data,
- Provide data to screens, workflows, and services,
- Define relationships between business objects,
- Support dropdowns, lookups, and validation, and
- Enable expressions, workflows, and processes to reference shared data consistently.
How the data model is used
Section titled “How the data model is used”The data model underpins all major parts of a Lowgile application:
- Screens read and write data using entities.
- Workflows move and transform data between steps.
- Expressions reference entity properties and relationships.
- Access control governs who can view or modify data.
A well-structured data model ensures that data flows consistently across the application.
Static vs transactional data
Section titled “Static vs transactional data”Lowgile separates entity data into two main categories to improve clarity, reuse, and data integrity:
1. Static entities
Section titled “1. Static entities”Static entities store controlled reference data. They:
- May be maintained manually or loaded dynamically from spreadsheets, integrations, or server-side scripts,
- Are used for dropdowns, lookups, validation, and shared reference data, and
- Include examples such as currencies, cost centers, countries, and engineering material lists.
2. Transactional entities
Section titled “2. Transactional entities”Transactional entities store user-driven data. They:
- Are created and updated as part of business processes,
- Represent real-world transactions, and
- Include examples such as PurchaseRequest and PurchaseRequestItem.
Key Takeaway
The data model is the foundation of every Lowgile application, and entities provide the shared data structures used throughout the runtime.
Designing it correctly ensures that:
- data is structured consistently,
- workflows operate reliably,
- screens display accurate information, and
- the application remains scalable and maintainable.
Invest time in designing your data model early, as it directly impacts every part of your application.