Reference & Data Model
Locks & delete protection
Which records Aligia protects against changes, what blocks deletion and how archiving cascades.
Approved times (freeze)
Section titled “Approved times (freeze)”Once a time log is „Genehmigt“ (approved), its date, description, billable flag, task, employee and project are locked; its time entries can neither be created, changed, moved nor deleted; the log itself cannot be deleted. The status remains changeable: withdraw the approval → edit → approve again. Reason: the personnel costs have been booked (Actual personnel costs).
System rows
Section titled “System rows”- Actual bookings are generally unchangeable for users (only the description of manual bookings may be changed); deletion is not possible. Correction via „Korrigieren“: a reversal row with a negative amount (description „Storno: …“), optionally a replacement booking.
- System-generated planned items are unchangeable and cannot be deleted; manual planned items are freely editable.
- The flag „Systemgeneriert“ can never be set afterwards.
Deletion: cascade, clear reference, block
Section titled “Deletion: cascade, clear reference, block”Deletion is a soft delete with preview. Before deleting, the system shows what will be deleted along and any conflicts:
| Conflict | Behavior |
|---|---|
| Approved time logs in the task / segment | Blocked – „1 freigegebener Zeiteintrag“ (1 approved time entry), withdraw the approvals first |
| Project that is not „Aktiv“ or not in an early phase | Blocked – „Projekt ist nicht aktiv oder nicht in einer frühen Phase“; way out: „Als fehlgeschlagen abschließen & archivieren“ (close as failed & archive) |
| Project with recorded items (costs/revenue, procurement, time entries, history) | Blocked – „{n} erfasste Vorgänge“ ({n} recorded items); way out: „Als fehlgeschlagen abschließen & archivieren“ |
| Committed optimization run on the project | Blocked – roll back the optimization first |
| Portfolio with projects or programs | Blocked – delete/move projects or delete programs first |
| Budget with cost item · Technical structure with project · Equipment unit with equipment · Good variant with procurement request, purchase, stock movement or technical component | Blocked – delete the dependent objects first |
Further rules per relation are on the entity pages (“On delete”: deleted along / reference cleared / kept / blocked). A deleted object can be restored together with the group deleted with it; cleared references (detach) stay cleared.
Archiving
Section titled “Archiving”Projects, programs and portfolios can be archived regardless of phase and status („Archivieren“ in the menu, banner „Dieses Objekt ist archiviert.“, „Wiederherstellen aus Archiv“). Children with the rule “archived along” (e.g. segments, tasks, costs, risks, members, reports of a project; projects and programs of a portfolio) are hidden along with it; children with “kept” (e.g. time logs of a project, projects of a program) are not. The preview shows both. Archiving does not change any KPI; the status decides which projects count.
Known limitations
Section titled “Known limitations”- No lock by role: anyone whose grant at the place allows it may delete, approve and archive (Access: who may do what).
- The freeze checks only user changes; system runs are exempt.
See Time log · Actual booking · Planned item · Common fields.