Task #19846
openTask #19866: Sprint Planning for 12/05/2026- 26/05/2026
Clearing - Create Air Clearing File from Scratch
0%
Description
Here, there is no quotation; data may be received via
- Paper documents
- External agents
Therefore, the user must be able to:
Create a clearing file WITHOUT any system reference.
User Flow¶
User clicks "Create Air Clearing File"
→ Does NOT select HAWB / MAWB / Quotation
→ System opens empty Clearing screen
→ User manually enters all required data
→ User clicks Save
→ Clearing File is created
Functional Requirements¶
1 – Manual Creation Mode¶
If user does NOT select:
- HAWB
- MAWB
- Quotation
Then system must:
- Allow full manual entry
2 – Mandatory Core Fields¶
User must enter the following before saving:
A. Shipment Details¶
| Field | Mandatory |
|---|---|
| Cargo Type (Import / Export) | ✅ |
| Origin Airport | ✅ |
| Destination Airport | ✅ |
| Shipment Type (Direct / Transit) | ✅ |
B. Flight Information¶
| Field | Mandatory |
|---|---|
| Airline | ✅ |
| Flight Number | Optional |
| ETD | Optional |
| ETA | Optional |
C. Party Information¶
| Field | Mandatory |
|---|---|
| Consignee | ✅ |
| Shipper | Optional |
| Notify Party | Optional |
3 – Optional Reference Fields¶
User may optionally enter:
- HAWB Reference (manual)
- MAWB Reference (manual)
These should NOT trigger linkage with shipment modules
4 – Data Validation¶
System must validate:
- Airports must be valid IATA codes
- Airline must exist in airline master
- Cargo Type must be selected
5 – Save Clearing File¶
When user clicks Save:
System must:
- Generate Clearing Reference
- Save all entered data
- Set status = DRAFT
6 – Activity Log Entry¶
System must log:
<username> created Clearing File <CLEARING_REF>
7 – Editing Behaviour¶
After saving:
- User can continue editing
- No restriction based on source
8 – No Dependency on Other Modules¶
Manual clearing must:
- NOT depend on:
- HAWB module
- MAWB module
- Quotation module
9 – Error Handling¶
If required fields are missing:
Display message:
Please complete all mandatory fields before saving.
Validation Rules¶
| Field | Rule |
|---|---|
| Cargo Type | Must be Import or Export |
| Airports | Must be valid IATA codes |
| Airline | Must exist in airline master |
| Consignee | Mandatory |
| Origin/Destination | Mandatory |
Acceptance Criteria¶
1 – Manual Mode¶
Given I open Create Air Clearing File,
When I do not select any reference,
Then the system should allow manual entry.
2 – Empty Screen¶
Given manual mode is active,
When the screen loads,
Then all fields should be empty.
3 – Mandatory Fields Validation¶
Given minimum required fields are missing,
When I click Save,
Then the system should prevent saving and display validation message.
4 – Save Manual Clearing File¶
Given all required fields are entered,
When I click Save,
Then the system should create a clearing file with status DRAFT.
5 – Activity Log¶
Given a manual clearing file is created,
When save is successful,
Then the system should log the creation activity.
6 – Optional References¶
Given I enter HAWB or MAWB manually,
When I save,
Then the system should save them as text only and not link to shipment records.
GitLab Sync Log
[{"id": "44690", "author": "Gilles Mahomudally", "hours": 7.0, "created": "2026-05-19T06:12:18.432Z", "log_date": "2026-05-18", "comment": "Imported from GitLab by @Gilles Mahomudally on 2026-05-19T06:12:18.432Z: 7h-(7.0)h spend at: 2026-05-18", "status": "active", "deleted_by": "", "redmine_entry_id": 13658}, {"id": "44689", "author": "Gilles Mahomudally", "hours": 7.0, "created": "2026-05-19T06:12:05.548Z", "log_date": "2026-05-17", "comment": "Imported from GitLab by @Gilles Mahomudally on 2026-05-19T06:12:05.548Z: 7h-(7.0)h spend at: 2026-05-17", "status": "active", "deleted_by": "", "redmine_entry_id": 13659}]
Updated by Redmine Admin 4 months ago
- Parent task set to #19866
- gitlab project trace set to Sprint Planning for 12/05/2026- 26/05/2026
Updated by Redmine Admin 3 months ago
- GitLab Time Logged changed from 0 to 50400