Service Records - Fields
Records in the service tracking system
have various pieces of information recorded with them, referred to as "fields".
Many are self-explanatory, however there are some deserving explanation.
This is especially so when specifying field names when customizing queries.
There are specialized field names,
and a general syntax
for specifying field names.
Here is a description of a subset of the possible fields,
identified by the title used when displaying their values.
Note that the names won't necessarily work when
specifying field names to display or sort.
For that, use the names in the parenthesized list.
- Account Number
(sponsors, Sponsors, Why, ?)
- Assigned By
- Audited By
- Cost Estimate
(cost_estimate, Cost Estimate, $?)
- Date Acted
- Date Created
- Date Due
(date_due, Date Due, Due Date)
- Date Start
(date_start, Date Start, Start Date)
- Date Time Worked
(date_time_worked, Date Time Worked)
- Date Worked
(date_worked, Date Worked, Worked)
- Effective Due
(date_due_eff, Effective Due)
(department, Department, Dept, Unit)
- Machine Name
(equip_name, Hostname, MachineName)
- Other IDs
(priority, Priority, !)
- Private Content
(requestors, Requestor, Req.)
- See Also
- Serial Number
(Serial #, #)
- Since Acted
(since_acted, Last Acted, last acted )
- Since Time Worked
- Since Worked
(since_worked, Last, Last Worked, last, last worked)
- Subscription Code
(subscription_code, Subscription Code)
- Time Worked
(time_worked, Time Worked)
- Transaction History — not a field, per-se
- Type of Work
(queue_id, Queue, Q)
(urgency, Urgency, Urg)
In addition, there are a few values represented as fields in messages,
that aren't fields in a service record, rather they are derived from fields
in the inventory system.
They use classic "X-" syntax, to identify them as
external to the service records.