hd:tech
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
hd:tech [2005/09/24 21:58] – (old revision restored) 127.0.0.1 | hd:tech [2021/04/14 09:34] (current) – fgm | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== HD Techs ===== | ===== HD Techs ===== | ||
- | < | ||
- | |||
HD Techs | HD Techs | ||
- | * process queries submitted by [[USER]]s, possibly prefiltered by [[ATTENDANT]]s. | + | * process queries submitted by [[USER]]s, possibly prefiltered by [[ATTENDANT]]s. |
* encode actual contracts as HD [[CONTRACT]] objects | * encode actual contracts as HD [[CONTRACT]] objects | ||
* manage the life of [[CONTRACT]] objects | * manage the life of [[CONTRACT]] objects | ||
They can either access the query list on site (from the start) or (later) receive notifications from it: | They can either access the query list on site (from the start) or (later) receive notifications from it: | ||
- | * new [[TICKET]]s | + | * new [[TICKET]] |
- | * new [[FOLLOWUP]]s | + | * new [[FOLLOWUP]] |
- | * closed [[TICKET]]s | + | * closed [[TICKET]] |
Notifications can be | Notifications can be | ||
Line 19: | Line 17: | ||
It is expected that synchronous notifications (email, SMS) will be triggered according to ticket status and/or severity. | It is expected that synchronous notifications (email, SMS) will be triggered according to ticket status and/or severity. | ||
- | [[TECH]]s | + | Techs are also the only ones able to created reverse tickets and followups, that recharge the support [[CONTRACT]]s instead of charging against them as all other [[TICKET]]s and [[FOLLOWUP]]s do. |
hd/tech.1127599085.txt.gz · Last modified: 2020/11/23 17:23 (external edit)