Shipper Interface
From UG
(→BR: Requirements) |
(→BR: Business Requirements and Design Ideas) |
||
Line 25: | Line 25: | ||
''This wiki section is managed by: [[Business Analyst]]'' | ''This wiki section is managed by: [[Business Analyst]]'' | ||
+ | Required core functionality: | ||
- | + | * password protected web based access to below | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
* add, edit, delete, view CTs | * add, edit, delete, view CTs | ||
* E Query functionality | * E Query functionality | ||
- | * Lock | + | * [[#BR: Lock for edit condition]] |
- | ==== BR: Add CT | + | === BR: Lock for edit condition === |
+ | |||
+ | Lock the record once a pick up trucker or estimated date is assigned | ||
+ | |||
+ | === BR: password protected web based access === | ||
+ | |||
+ | We realize that there are possibly 3 options: | ||
+ | |||
+ | a) to "trim down" Internal App | ||
+ | b) to "expand" Client App | ||
+ | c) create separate App | ||
+ | |||
+ | It is up to Dev to decide which way to go because one of the requirements here is "to create this module ASAP". So we can sacrifice "style" for speed if necessary. | ||
+ | |||
+ | We assumed that option "b" is most probable that is why some requirements are formulated based on this assumption. | ||
+ | |||
+ | === BR: Add CT === | ||
System should generate CT# and let shipper user enter some CT2 fields (some fields will be set by the system): | System should generate CT# and let shipper user enter some CT2 fields (some fields will be set by the system): | ||
Line 78: | Line 91: | ||
* Cargo Due: | * Cargo Due: | ||
- | + | === BR: Edit CT === | |
+ | |||
+ | Ability to open record and edit fields above unless [[#BR: Lock for edit condition]] is true. | ||
+ | |||
+ | After record is locked show read-only version. | ||
+ | |||
+ | === BR: Delete CT === | ||
- | + | === BR: View CTs === | |
- | |||
- | |||
Revision as of 17:59, 28 May 2010
Contents |
Intro
This is a new module therefore at this moment it is not clear what components are required or affected. As a result all requirements are documented in this "main" article for now.
CBN: Core Business Need
This wiki section is managed by: Module Owner
Core business need is to "outsource" entering of new CTs to Vendors (Shippers). This supposed to:
- 1) significantly cut man hours in Jaguar
- 2) streamline / minimize communications
Later (in 1-3 months) some other functions should be provided to Vendors like "approval feature".
BR: Business Requirements and Design Ideas
This wiki section is managed by: Business Analyst
Required core functionality:
- password protected web based access to below
- add, edit, delete, view CTs
- E Query functionality
- #BR: Lock for edit condition
BR: Lock for edit condition
Lock the record once a pick up trucker or estimated date is assigned
BR: password protected web based access
We realize that there are possibly 3 options:
a) to "trim down" Internal App b) to "expand" Client App c) create separate App
It is up to Dev to decide which way to go because one of the requirements here is "to create this module ASAP". So we can sacrifice "style" for speed if necessary.
We assumed that option "b" is most probable that is why some requirements are formulated based on this assumption.
BR: Add CT
System should generate CT# and let shipper user enter some CT2 fields (some fields will be set by the system):
- E0. Client Company:
- required
- system sets it automatically to E.A. USA Domestic (not visible)
- E1
- system sets it automatically to Elizabeth Arden
- (not visible)
- E2
- Based on log in, copy from "Part B. Visibility, E0. Client Company" in user profile (design idea)
- C. Customer Ref #:
- 2. Shipper (T1):
- pre-filled based on login company (not visible)
- 5. Export Pick-up (T4):
- same as on internal but only USA/Canada
- 3. Consignee (T2):
- same as on internal but only USA/Canada
- Created by
- not editable
- Created on time
- new field see mantis
- Created on date
- make it visible
- 7. Pick-up Comments:
- 15. Commodity description:
- Cargo Available:
- Cargo Due:
BR: Edit CT
Ability to open record and edit fields above unless #BR: Lock for edit condition is true.
After record is locked show read-only version.
BR: Delete CT
BR: View CTs
</div>