Object Movement Reason
A movement reason explains a service object movement ("received for repair", "returned to customer", "moved to yard") and decides which photos the movement must carry.
What it is for
When a Service Object Movement is created with this reason, each ticked photo (Front, Back, Left, Right, Up, Down) becomes required on the movement.
Process Code and Required Prcoess Number are stored only; no save reads them.
Every field in plain words
| Field | What it means | What to put |
|---|---|---|
| Movement Reason | The code or number of this record | A short unique code, or the next number when a number range is set up. Required. Cannot be changed once saved |
| Name | The name | Free text. Required |
| Process Code | A screen code | Recorded only |
| Required Prcoess Number | Process number flag | Recorded only |
Images Required
| Field | What it means | What to put |
|---|---|---|
| Front | A front photo is required | Tick to require it |
| Back | A back photo is required | Tick to require it |
| Left | A left photo is required | Tick to require it |
| Right | A right photo is required | Tick to require it |
| Up | A photo from above is required | Tick to require it |
| Down | A photo from below is required | Tick to require it |
How to configure it
Add one reason per kind of movement. Tick the photos the yard must take for that reason.
Scenarios
- A container depot photographs all four sides on receipt. Reason "Gate in" with Front, Back, Left and Right ticked.
What it is connected to
- Service Object Movement - Movement Reason.
- Object Inspection Template - the same photo ticks for inspections.
If something looks wrong
- A movement asks for a photo nobody takes. The photo is ticked on its reason. Clear it here.