The actual list of operation types, fields, and conditions. For step-by-step actions, see Performing asset operations; for how it all works, see Asset operations.
| Operation | Code (doc_type) | What it does |
|---|
| Check Out | checkout | Issue an asset from a location to an employee |
| Check In | checkin | Receive an asset from an employee into a location |
| Transfer | location_transfer | Move an asset from one location to another |
| Send to service | service_out | Send an asset to a service center |
| Return from service | service_in | Receive an asset back from a service center |
| Operation | From the asset card | From the “CheckIn/CheckOut” section |
|---|
| Check Out | yes | yes |
| Check In | yes | yes |
| Transfer | yes | yes |
| Send to service | yes | no |
| Return from service | yes | no |
From the asset card, an operation handles a single asset. In the CheckIn/CheckOut section, a single document can cover several assets.
| Current asset state | Available actions |
|---|
| With an employee | Check In; Send to service |
| At a location | Check Out; Transfer; Send to service |
| In Maintenance | Return from service |
| Pending Disposal | no operations |
| Field | Required | Description |
|---|
| Responsible person | yes | The employee receiving the asset |
| Planned return date | no | Expected return date |
| Notes | no | Free-form comment |
| Field | Required | Description |
|---|
| Location of the asset when relocated | yes | Where the asset is placed |
| Condition | no | See “Condition values” |
| Notes | no | Free-form comment |
| Field | Required | Description |
|---|
| Source Location | — | Current location, read-only |
| Target Location | yes | Where the asset is moved to |
| Condition | no | See “Condition values” |
| Notes | no | Free-form comment |
| Field | Required | Description |
|---|
| Service Options | yes | Mode: “Make Item Unavailable” or “Do not make item unavailable” |
| Scheduled date of return | no | Only in “Make Item Unavailable” mode |
| Date of transfer to service | no | Only in “Do not make item unavailable” mode |
| Date of return from the service | no | Only in “Do not make item unavailable” mode |
| Repair cost | no | Only in “Do not make item unavailable” mode |
| Service Center | no | An existing center or a new name |
| Fault description | no | Description of the problem when sending |
| Description of the problem from the service | no | Only in “Do not make item unavailable” mode |
| Materials used | no | Materials from the Inventory module |
| Field | Required | Description |
|---|
| Return to | yes | Holder type: “Employee” or “Location”, then the holder itself |
| Repair cost | no | Cost of the repair done |
| Description of the problem from the service | no | What the service did |
| Materials used | no | Materials from the Inventory module |
| Mode | What happens |
|---|
| Make Item Unavailable | The asset is moved to the “In Maintenance” status and becomes unavailable |
| Do not make item unavailable | The status does not change; only a service record is created |
System condition values. The set is configured in Asset statuses and conditions.
| Condition | Code |
|---|
| New | new |
| Good | good |
| Satisfactory | satisfactory |
| Poor | poor |
| Damaged | damaged |
| Non-functional | non_functional |
If no condition is selected, the card shows “Not specified”.
| Condition | Value |
|---|
| How to write off | Move the asset to a write-off location |
| Status after write-off | ”Pending Disposal” (pending_disposal) |
| When deletion is available | Only for assets in a write-off location |
| Where to delete | The delete icon (trash can) in the location’s asset list |
| Reversibility | Deletion is irreversible; related data is deleted along with the asset |
| Permission | What it allows |
|---|
transfers.view | View the “CheckIn/CheckOut” section and transfer documents |
transfers.create | Create operations (the Action button on the card and the buttons in the “CheckIn/CheckOut” section) |
Permissions are assigned through the user’s role.
