Reference & Data Model
Data flow: live synchronization and system data
What you change, everyone sees immediately. Some data is written only by the server; it is recognizable as „vom System erzeugt“ (generated by the system).
Live synchronization
Section titled “Live synchronization”Aligia keeps a local copy of your organization’s business data on your device. Every change you make is first saved locally, shown immediately and then transmitted to the server. The server distributes every change to all other connected devices. If a colleague changes the title of a task, you see the new title without reloading. If the connection drops, you keep working; the changes are submitted as soon as the connection is back. After an interruption Aligia fully reconciles the state so that no change is missing.
Two practical consequences:
- Deleting needs a connection, archiving does not (see Lifecycle).
- A record that is „Noch nicht synchronisiert“ (Not yet synchronized) cannot be deleted for a short while; wait a moment.
What only the server writes
Section titled “What only the server writes”Some data does not arise from input but from rules on the server. It is synchronized live to you like all other data, but cannot be edited, or only to a limited extent:
| Data | Written by | How to recognize |
|---|---|---|
KPI values (kpi_value) |
The server’s KPI pipeline; recalculated as soon as a source changes, with a freshness budget of 60 seconds | read-only; scoreboards and dashboards show them |
| Derived records: system-generated actual bookings and plan items, procurement requests from material requirements, default cost items of a new project | The server’s derivation rules; the system keeps a register (system_derived_record) that links every generated row with its source and rule |
Label „Systemgeneriert“ (System-generated) instead of „Manuell“ (Manual) in the „Erstellungsart“ (Creation type) column; not editable |
| Bookings of the optimizer (employees, equipment) and optimizer dates on project and task | Optimizer when applying a result | in the activity history with „Optimierung übernommen“ (Optimization applied) / „Optimierung zurückgesetzt“ (Optimization reset) |
| Internal fields of conversations, executions, file versions and storage locations | Agent engine, workflow engine, upload | not visible |
The register of derived records ensures that a change at the source updates the derived record: if the planned effort changes, the planned personnel cost item changes; a purchase in base class „Bestellt“ or „Geliefert“ keeps its material cost booking current, and if it becomes invalid or is deleted, the system retracts the booking. Which rule generates what is described in chapter 12; the overview of derived records in Derived records.
„Vom System erzeugt“ as a marker
Section titled “„Vom System erzeugt“ as a marker”Wherever this part marks a field or a record with System, the following applies: you can see the value but not set it directly. Examples are a project’s priority rank, the dates calculated by the optimizer, the label „Systemgeneriert“ on a booking and every KPI value. If you want to change such a value, change the source: the planned effort, the purchase, the time log. KPIs and their calculation are explained in chapter 13.