Skip to content

Reference & Data Model

Lifecycle of a record

Create, edit, archive, delete: every record goes through the same steps. What happens to related records is defined per relation.

Create ──▶ Edit ──▶ Archive ⇄ Restore
│ │
└──────────┴──▶ Delete (permanent, with preview)
  • Create: via a dialog or a „Neu“ (New) button. Required fields must be filled.
  • Edit: directly in the profile, sheet or table. Changes take effect immediately and everywhere, see Data flow.
  • Archive: hides the record and everything below it everywhere. Nothing is lost; „Wiederherstellen aus Archiv“ (Restore from archive) reverses the step. Also works offline. Archiving does not change any KPI.
  • Delete: removes the record and all dependent data permanently. Needs a connection, because Aligia first determines the scope and shows it as a preview („Geschätzter Umfang“ / „Exakter Umfang“ (Estimated scope / Exact scope), „{n} betroffene Einträge“ ({n} affected entries)). Right afterwards there is a brief „Rückgängig“ (Undo). If there is no connection, Aligia offers „Stattdessen archivieren“ (Archive instead). A project can be deleted only under narrow conditions, see below.

Archivable are, among others, Portfolio, Program, Project, Segment, Work package, Task, Subtask, Milestone, Gate, Event, Project member, Material requirement, Cost item, Bookings, Risks, Opportunities, Measures, Status reports, Key takeaways, Time log, Issue, Folder, Skill of an agent and Workflow definition. Master data such as Employee, Material or Equipment have the field Active instead.

For every “belongs to” relation it is defined what happens to the dependent record when the target is deleted and, where the entity is archivable, what happens on archiving. The entity pages name the rule per relation.

Rule Business meaning On delete On archive Documented example
deleted along / archived along (cascade) The dependent record only exists with its target. is deleted along is archived along Segment → Project: deleting or archiving the project deletes or archives all segments, tasks, milestones and gates.
reference cleared (detach) The dependent record remains, it only loses the reference. reference is cleared – Task → Work package: if the work package is deleted, the task remains in the segment, just without a work package. Likewise Project → Project manager.
kept (keep) The dependent record remains unchanged, including the reference. kept stays active Time log → Employee; Task → assigned project member; Project → Program when the program is archived.
blocked (restrict) The target must not be deleted as long as dependents exist. deletion is blocked, the preview shows „{n} abhängige Datensätze verhindern das Löschen.“ ({n} dependent records prevent deletion.) – Portfolio with projects or programs („Projekte zuerst löschen oder in ein anderes Portfolio verschieben.“ (Delete projects first or move them to another portfolio.)); Budget with cost items; Variant with purchases or procurement requests; Technical structure with projects.

How common the rules are: of around 210 relations in the data model, about 110 delete along (cascade), around 50 clear the reference (detach), around 25 are kept (keep) and 9 block deletion (restrict). On archiving there are only two rules: around 55 relations archive along, around 35 are kept. In the delete preview the groups are called „Verlieren die Verknüpfung“ (Lose the link) (detach) and „Bleiben aktiv“ (Stay active) (keep).

Two locks apply independently of the rules above:

  • Approved times. A time log with status „Genehmigt“ (Approved) is frozen: date, description, billable, task, employee and project cannot be changed, nor can its time entries, and it cannot be deleted. Reason: personnel costs were booked from the approval. Correct way: withdraw the approval, change, approve again. A task or a segment with approved times cannot be deleted: the preview reports „1 freigegebener Zeiteintrag“ (1 approved time entry) („Freigabe zurücknehmen oder Objekt behalten.“ (Withdraw approval or keep object.)); withdraw the approvals first.
  • System-generated bookings. An actual booking or plan item that the system generated („Systemgeneriert“) cannot be edited or turned into a manual one. For actual bookings, additionally only the description can be changed afterwards; amount and date are fixed. Details in Locks.

A project can be deleted only while it is „Aktiv“ (Active), in an early phase (Initialization, Definition, Planning), has no committed optimization run and nothing has been recorded: no costs/revenue, no procurement, no time entries, no history. Otherwise the preview reports „Projekt ist nicht aktiv oder nicht in einer frühen Phase“ (Project is not active or not in an early phase), „{n} erfasste Vorgänge“ ({n} recorded items) or „1 festgeschriebener Optimierungslauf“ (1 committed optimization run), and Aligia offers „Als fehlgeschlagen abschließen & archivieren“ (close as failed & archive). You roll back a committed run first, see Applying the optimizer. For the status see Project.