Project

General

Profile

Actions

Task #19872

open

Clearing - Party Information Section

Added by Redmine Admin 4 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
05/08/2026
Due date:
05/08/2026 (about 4 months late)
% Done:

0%

Estimated time:
0:00 h
GitLab ID:
4402
GitLab Milestone:
GitLab Ticket Number:
1519
GitLab Time Logged:
0
Lock Timeline Date:
No
gitlab project trace:

Description

In freight clearing, “party information” means the companies or persons involved in the shipment.

Common parties are:

Party Simple Meaning
Shipper The person/company sending the goods
Consignee The person/company receiving the goods
Notify Party The person/company to be notified about the shipment
Clearing Agent The company handling customs clearance
Delivery Agent The company/person handling final delivery, if applicable

Screen Section

Section Name: Party Information

This section should appear after Flight Information on the Air Clearing Add/Update screen.

The Party Information section contains multiple tabs representing different shipment parties.

The same screen structure will be used for:

  • Air Import
  • Air Export

The labels may dynamically adapt depending on Cargo Type.

Tabs Required

The section must contain the following tabs:

Tab Purpose
Shipper Sender/exporter of goods
Consignee Receiver/importer of goods
Notify Primary notify party
Notify 1 Secondary notify party
Delivery Agent Delivery or handling agent

Common Structure for All Tabs

Each tab must contain the same structure/layout.

Fields per Tab

Field Type Mandatory Remarks
Choose Existing Party Button- Shipper/consignee, etc. Button No Opens party selection popup
Individual / Company Toggle button Yes Determines party type
Company Name / Name Textbox Conditional Depends on Individual/Company
Contact Person / Name 2 Textbox No Secondary name/contact
BRN Textbox No Business Registration Number
Phone Textbox No Phone number
Email Address Textbox No Email
Address Textbox No Main address
Address 2 Textbox No Additional address
Address 3 Textbox No Additional address

Functional Requirements

1 – Display Tab Structure

The system must display all party tabs inside the "Shipper / Consignee / Notify Party Information" section.

Tabs:

  • Shipper / Exporter
  • Consignee / Importer
  • Notify
  • Notify 1
  • Delivery Agent

2 – Shared Layout Across Tabs

All tabs must use the same field structure/layout.

3 – Choose Existing Party Button

Each tab must contain a button:

Example:

Choose existing shipper

Choose existing consignee

Choose existing notifier

Choose existing delivery agent

When clicked:

  • System opens party selection popup
  • User selects existing party from master
  • System auto-populates fields

4 – Party Selection Popup

The popup should support searching existing parties by:

  • Company Name

5 – Individual / Company Toggle

Each tab must allow user to select:

IndividualCompany

Behaviour

If Individual selected:

  • Company Name label changes to Name
  • BRN may become optional/not applicable

If Company selected:

  • Company Name remains visible
  • BRN applicable

6 – Auto-populate Party Details

When user selects an existing party:

System should auto-populate:

  • Name / Company Name
  • Contact Person
  • BRN
  • Phone
  • Email
  • Address fields

7 – Mandatory Party Rules

Air Import

Party Mandatory
Consignee / Importer Yes
Shipper / Exporter Optional
Customer/Bill To Yes

Air Export

Party Mandatory
Shipper / Exporter Yes
Consignee / Importer Optional
Customer/Bill To Yes

8 – Notify Parties

The system must support:

  • Notify
  • Notify 1

These are separate parties and is optional.

They may:

  • Be same as consignee
  • Be different parties

No duplicate restriction required.

9 – Delivery Agent

Delivery Agent tab is optional.

Used when:

  • Cargo delivery handled by third party
  • Delivery coordination required

10 – Save Party Information

When user saves Air Clearing File:

  • All tab information must be saved
  • Party linkage and snapshot details preserved

12 – Activity Log

When party information is modified after first save:

System must create Activity Log entry:

updated party information for Air Clearing File <CLEARING_REF>

Activity Log is displayed at the bottom of the Air Clearing Add/Update page.

Validation Rules

Field Validation
Individual/Company Mandatory
Consignee/Importer Mandatory for Air Import
Shipper/Exporter Mandatory for Air Export
Email Must be valid format
BRN Optional
Phone Numeric/supported phone format

Error Messages

Scenario Message
Missing Import Consignee Please complete Consignee / Importer information.
Missing Export Shipper Please complete Shipper / Exporter information.
Invalid email Please enter a valid email address.
Missing Individual/Company Please select Individual or Company.

Acceptance Criteria

1 – Display Tabs

Given I open an Air Clearing File,
When the page loads,
Then the system should display all party tabs.

2 – Select Existing Party

Given I click “Choose existing shipper”,
When I select a party,
Then the system should auto-populate shipper fields.

3 – Individual Toggle

Given I select “Individual”,
When the tab refreshes,
Then the Company Name field should behave as Name field.

4 – Company Toggle

Given I select “Company”,
When the tab refreshes,
Then Company Name and BRN fields should be applicable.

5 – Import Validation

Given Cargo Type = Import,
When Consignee / Importer is blank and I click Save,
Then the system should display error information.

6 – Export Validation

Given Cargo Type = Export,
When Shipper / Exporter is blank and I click Save,
Then the system should display error information.

7 – Editable Fields

Given party data is auto-populated,
When I modify address or contact details,
Then the system should allow editing.

8 – Save Party Information

Given all required party details are entered,
When I save the Air Clearing File,
Then the system should save all tab information successfully.

9 – Activity Log

Given party information is updated after initial save,
When I save changes,
Then the system should record the update in Activity Log.


GitLab Sync Log

[]

Actions

Also available in: Atom PDF