Requests
–
| Request Request.RequestIdTicket.TicketKey | Service user | Type RequestType.NameTicket.Category | Status RequestState.NameTicket.Status | Next action by Request.NextActionDate | Assigned Request.AssignedToTicket.AssigneeUserId | Priority RequestPriority.NameTicket.Priority | Actions |
|---|
Tickets are born in the ARC and carry the purple source pill; only SM requests are created here. Tickets and SM requests are not linked — they co-exist in the one queue (Zori 10 Sep).
Requests › Request
Tasks
the work units — a request completes when its tasks do Add task| Task TaskType.Name | Scheduled Task.StartTime | Assigned Task.AssignedTo | Status | Actions |
|---|
No tasks yet — add the first one.
A new task starts unscheduled and is booked from Scheduling; its expected duration defaults from the task type. Holding a task holds the whole request.
Equipment
the devices this request affects — linked to the request, not its tasks| Product Stock.ModelName | Serial StockItem.SerialNo | Role on this request StockItemRequest |
|---|
No unit picked yet. The equipment is chosen when the request completes — Delta doesn't pre-allocate (D24-21).
Installed units come from the service user's Equipment tab; a reserved unit is released if the request is cancelled.
Notes
Request has no description column — free text is a linked note Note.Requests.
Details
Actions
Requests › Ticket
Description
—
Comments
0
Comments are the ARC's TicketComment.Body — visible to the ARC operators too.
Audit
| When TicketAudit.CreateDate | Action | By | Details TicketAudit.Details |
|---|
Read-only trail from the ARC — the user-level who-did-what reporting Delta asked for.
Details
Attachments
| File TicketAttachment.FileName | Size |
|---|
No attachments.
Actions
Creates an SM request for the field work. No link is stored — the ticket and the request co-exist (Zori 10 Sep).