Intake
An incoming submission kept intact through triage and classification.
Keep the original Description, Source Kind and Evidence. Related Configuration links the schedule involved. Classification can link a Milestone, Task or Incident while retaining the original submission. This table is distinct from intake views, which are filtered queues on other tables. No workflow classifies intakes automatically.
Use and boundaries
Field names below are the current product labels. * and ° are UI markers, not database constraints. A preferred single-record selection is not a global cardinality constraint either. The related guide explains operational rules.
Fields
| Field | Storage | Source, options or boundary |
|---|---|---|
| Name | Text | Stored value. |
| Source Kind | Text | Stored value. |
| Description | Long text | Stored value. |
| Source Root Cause | Long text | Stored value. |
| Related Configuration | Linked records | Recurrence Configuration |
| Evidence | Attachments | Stored value. |
| Triage | Long text | Stored value. |
| Due Date | Date | Stored value. |
| Lifecycle Status | Single select | Draft, Proposed, Active, On Hold, Completed, Cancelled, Archived |
| Resolution Plan | Long text | Stored value. |
| Classified As (Milestone) | Linked records | Milestone |
| Classified As (Task) | Linked records | Task |
| Classified As (Incident) | Linked records | Incident |
| Tags | Linked records | op:tags · optional labels from the Core Tags catalog; classification only. |
Example and maintenance
Illustrative example: “Missing report request” preserves the original feedback and links the Task created after triage.
Use the existing fictitious records to inspect relationships in the guide. Before changing fields, check lookups, formulas, intakes and workflow contracts. This page documents structure; a field does not prove that an integration populates it.