Business Objects - Operations

This section describes the operations entities managed by the application and their relationships.

Entities

To illustrate which Project it belongs to, the project appears in the diagram, but it is actually the one from the core module.

• Project
  • Movement
    • Communication (movement with activity only)
  • Alert
    • Communication
  • Participant
    • Comment
      • Tag (project-scoped catalog)
    • Completion Notice (0..1 Internal, 0..1 External)

Structure

Dot relationships ( ..) are used to indicate that related entities are from another module, while solid relationships ( --) indicate entities from the same module. All elements are scoped to a project, but for readability we only show the project relationship on top-level entities (movement, alert, etc.).

Editability of Operations entities

Movement is the only immutable entity in the Operations module. Every other entity supports in-place editing.

Entity	Editability
Movement	Immutable. No edit feature. To correct, soft-delete with Hide movement and record a new one.
Communication	In-place edit of the message (Edit communication).
Alert	In-place edit of title, description, and status (Edit alert).
Comment	In-place edit of message and tags (Edit comment). Delete with Delete comment.
Completion Notice	Editable in DRAFT only. Once PUBLISHED, the notice becomes immutable. See Create, Edit, Publish.

Why Movement is special

The Movement log is the audit trail of entries and exits at the site. It must reflect what actually happened, so edits after the fact are forbidden — corrections go through a soft-delete of the erroneous movement and a new one. All other Operations entities are working annotations on top of that log and can be edited in place.