Core TSIs : Work Orders : Impact of field changes in orders : Field change sequence in Work Orders
Field change sequence in Work Orders
If you modify field data at the Orders selection level, other field data may change automatically, because (default) data of one element is dependent on (default) data of another element. If a series of automatic changes takes place, some data changes take precedence over other data changes. The following table specifies which field data 'outrank' other field data.
* 
Field data which is linked to high-ranking elements (i.e. those with the highest numbers) will overwrite the data of lower-ranking elements.
As you can see, data in the Priority field can be overwritten quite easily, while Standard order data will overwrite the default data of most other elements, except those of Knowledge Base items. Refer to Field changes exemplified for some examples.
 Sequence
Modification of field value
10
Priority
11
Impact
12
Severity
20
Cost center
30
Department
40
External coordinator
50
External tradesperson
70
Space
80
Requestor (internal)
90
Work space
100
Asset
110
Reservation unit
115
Property
120
Order group
130
Trade
140
Externally assigned by
150
SLA service
160
Project
1000
Start date-time
1000
End date-time
1000
Person count
2000
Standard order
2100
Knowledge Base item
* 
Field changes that involve inheriting field values from other elements are not incorporated in this table.