Reference & Data Model
Follow-up data: criteria, agents, invitations
Three actions create further records in the background that you then see in the interface.
Criterion → assessment „Ausstehend“
Section titled “Criterion → assessment „Ausstehend“”Trigger: A new target criterion (portfolio_target) or risk criterion (risk_contribution) is created in the portfolio; or a project is created or moved to another portfolio.
What is created: Per project of the portfolio one target assessment (target_assessment) or risk contribution assessment (risk_contribution_assessment) with answer unset (shown as „Ausstehend“, pending), without assessor and date. When a project moves to another portfolio, assessments of foreign criteria are deleted and missing ones added.
On rollback: Deleting a criterion deletes its assessments (cascade). Deleting a criterion without creating a new one lets the priority calculation continue with the remaining criteria.
Where visible: Project profile, section target/risk contribution; portfolio › Strategie (Guides › Criteria).
Limitation: Creation runs in the client of the person saving the criterion or project. If the operation aborts, rows are missing; the next save of the project repairs that.
Activate agent → user account
Section titled “Activate agent → user account”Trigger: An agent (agent) is set to „Aktiv“ (owner/admin only).
Condition: Name not empty, model enabled in the organization.
What is created: A user (app_user, origin agent), once per agent; on re-activation the same one is reactivated. The active status on the agent is set exclusively by the server.
On rollback: „Inaktiv“ deactivates the user account (active = false) but does not delete it; the assignment remains.
Where visible: Automation › Agenten; the account appears as creator in conversations (Guides › Agents).
Invitation → employee stub
Section titled “Invitation → employee stub”Trigger: Owner/admin invites a member and chooses „Neuer Mitarbeiter“ (first name, last name) instead of an existing one.
What is created: Immediately an employee (employee) with name and e-mail (idempotent per e-mail: a repetition does not create a second one). When the invitation is accepted, the employee is linked to the new user account (employee.app_user_id). Without an explicit choice, Aligia links on acceptance when exactly one unlinked employee has the same e-mail.
On rollback: Withdrawing the invitation does not delete the stub.
Where visible: Einstellungen › Organisation › Mitglieder; Stammdaten › Mitarbeiter (Guides › Invite member, Guides › Employees).
See Portfolio target criterion · Risk contribution · Agent · User · Employee.