Manufacturing › Batch Records
Batch Signatures
Who signed what, and what the signature MEANT. The signed content is hashed, so a later edit would not match — and there is no update path, because that is what a signature is.
Where to find it
- Module: Manufacturing
- Group: Make
- Section: Batch Records
- Screen: Batch Signatures
Address in the console: /mfg/batch-signatures
Read-only list · 9 columns
This list is read-only: its records are written by the work that produces them. A correction, where one is possible at all, is made where the record was created.
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| When | Date and time | signed_at |
| Batch | Code | batch_no |
| Step | Number | phase_no |
| Meaning | Status | meaning |
| Signed by | Text | signer_name |
| As | Text | signer_role |
| Proven by | Status | auth_method |
| What was signed | Text | signed_summary |
| Hash | Code | signed_hash |
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.