A bad container number or wrong file type at the gate burns minutes. Operators need validation on the number, clear file rules, and a way to fix a bad submit without starting over.
Create a package with validated container and files
Create package binds a container number to uploaded documents. Supported types, unsupported-type errors, submit loading, and invalid-container recovery keep the yard flow moving.
Enter container number
Empty create form with container number field.
Implementation narrative
Create package opens with a container number field. A checkmark marks a valid ID; the upload zone accepts doc, pdf, xlsx, zip, png, and jpg. Unsupported types trigger a red banner. Attached files show type icons with download and delete. Save enters a loading state, then the registry shows the new rows. Invalid container numbers surface an edit-and-send recovery card.
- Enter container number: Empty create form with container number field.
- Validated container, empty files: Checkmark on the ID and dashed upload zone for documents.
- Reject unsupported type: Red banner lists allowed doc pdf xlsx zip png jpg types.
- Attach documents: Type-coded file rows with download and delete actions.
- Save in progress: Bottom save control shows loading while the package stores.
- Back on the registry: Active list shows new rows with request-documents actions.
- Invalid container recovery: Error card with edit-and-send and delete for a bad number.