Overview

The aeppic data model forms the backbone of the entire system, organizing all application data and configuration into a hierarchical tree of documents. At the core of the model is the root document, from which all other documents descend.

Why the Data Model Matters

The hierarchical structure of the data model provides:

• Organization: A clear structure for managing related data. It maps well to real-world business processes as those are inherently hierarchical.
• Flexibility: Documents and forms can be extended or modified as requirements evolve.
• Traceability: All changes to documents are always recorded in a change log and represent the final truth of all data.

Key Concepts

Documents

Documents are the basic building blocks of the data model. Each document:

• Represents a node in the tree.
• Stores data or configuration.
• Is defined by a schema (form).

Documents can:

• Be created, edited, moved, or deleted etc. via the API or the language specific libraries.
• Be parents to child documents, forming a hierarchical structure.

Learn more: Documents

Forms

Forms define the data structure and behavior of documents. A form:

• Acts as a schema, specifying the fields and validation rules for documents.
• Supports dynamic rendering in user interfaces.
• Can inform generic components of some desired behavior via tags and other properties.
• Are parents to form specific designs and commands.

Each document is based on a form, ensuring consistency across the application.

Learn more: Forms