|
|
(74 intermediate revisions not shown) |
Line 1: |
Line 1: |
- | [[Category: ClientEtc]] | + | [[Category:Cybertrax 2.1 Client]] |
| | | |
- | == Intro == | + | == Introduction == |
| | | |
- | This article describes solution through a set of use cases for Cybertrax ver 2.1 Client application a.k.a. Shipper Interface. | + | This article describes design (solution) for Cybertrax ver 2.1 Client application a.k.a. Shipper Interface. |
| | | |
- | This is based on [[Cybertrax 21 Client BR]] business requirements wiki.
| + | Design is based on business requirements documented in [[Cybertrax 2.1 Client (requirements)]]. |
| | | |
- | == Business Story One And Major Related Use Cases == | + | === Shipper Functionality === |
| + | Fully defined in: |
| + | * [[Cybertrax 2.1 Client (requirements)]] |
| + | * [[Cybertrax 2.1 Client (data dictionary)]] |
| + | * see also [[Cybertrax 2.1 Client (use cases)]] |
| | | |
- | ''Company Jackel is a supplier for a company CEI Holmdel. Accordingly to the new business process operator Mary Doe at Jackel is responsible for creating new shipments. All new shipments with PO issued by Arden Stamford have to go through authorization process by planner John at Arden in Stamford. If authorized then they are ready to enter into transportation phase and be handled by Jaguar operator Susan. It is also possible that they get rejected or put on hold. In addition supervisor Mike at Arden would like to monitor/run reports on all shipments created by Jackel.''
| + | === Planner Functionality === |
| + | Fully defined in: |
| + | * [[Cybertrax 2.1 Client (requirements)]] |
| + | * [[Cybertrax 2.1 Client (data dictionary)]] |
| + | * see also [[Cybertrax 2.1 Client (use cases)]] |
| | | |
- | ''On July 1, Mary has the following 2 products ready to ship from Gannet Warehouse in Edison, NJ, going to CEI in Holmdel, NJ. First Mary has PO # H018386, Sku 152813, packaged as 1 pallet, with 8 cartons, that contain 49,152 pcs inside, and weighs 108 pounds. Second, Mary has PO # HEA0043, Sku 135096, packaged as 4 pallet, with 50 cartons, that contain 40,000 pcs inside, and weighs 560 pounds.''
| + | === Jaguar User Functionality === |
| + | Fully defined in: |
| + | * [[Cybertrax 2.1 Client (requirements)]] |
| + | * [[Cybertrax 2.1 Client (data dictionary)]] |
| + | * see also [[Cybertrax 2.1 Client (use cases)]] |
| | | |
- | === Notes === | + | === Miscellaneous Functionality === |
- | | + | Fully defined in: |
- | In order to implement described business process in Cybertrax 2.1 we need to create users with appropriate roles:
| + | * [[Cybertrax 2.1 Client (requirements)]] |
- | * user mary@jackel.com with enabled “Shipper (a.k.a. Supplier) /Create Shipments Role” | + | * [[Cybertrax 2.1 Client (data dictionary)]] |
- | * user john@arden.com with enabled “Authorization/Planner Role”
| + | * see also [[Cybertrax 2.1 Client (use cases)]] |
- | * user susan@jaguarfreight.com with enabled “Jaguar Operator Role”
| + | |
- | * user mike@arden.com with enabled “Viewer (a.k.a. Client) Role”
| + | |
- | | + | |
- | Please note that current version Cybertrax 2.0 is based on another business process. Shipments are created by users with Jaguar Role (jaguar employees) only. At the same time read-only monitoring/reporting on shipments is supported (Client User role). Authorization is not part of this process.
| + | |
- | | + | |
- | === Use case. Create User Mary with a Create CT Role ===
| + | |
- | | + | |
- | Jaguar operations manager creates user mary@jackel.com with Supplier role. E0 Client Company field is set to EA USA Domestic. Shipper field is set to Jackel. See [[#Figure 1]].
| + | |
- | | + | |
- | | + | |
- | === Use case. Log In As a Supplier First time ===
| + | |
- | | + | |
- | Mary logs in. Her homepage is Shipments List, New Tab. No shipments displayed. See [[#Figure 3]].
| + | |
- | | + | |
- | === Use case. Create First Shipment ===
| + | |
- | | + | |
- | 1) Mary clicks on “Add” button. System offers empty form. Mary fills in all required fields. See [[#Figure 4]] | + | |
- | | + | |
- | 2) Mary clicks “Save” button and is presented with “Preview and Disclaimer Screen”. See [[#Figure 5]]
| + | |
- | | + | |
- | 3) She makes sure that all info is accurate, clicks OK and presented with “Confirmation screen”. See [[#Figure 6]]
| + | |
- | | + | |
- | 4) She clicks OK and System presents her with Shipments List. 3 new shipments appear now on New Tab. See [[#Figure 7]]
| + | |
- | | + | |
- | === Use case. Create User with Authorization/Planner Role ===
| + | |
- | | + | |
- | Jaguar operations manager creates user john@arden.com with Planner role. “Authorize CT with PO issued by” field is set to “EA Stamford” . See [[#Figure 2]].
| + | |
- | | + | |
- | === Use case. Log In As a Planner and see shipments to authorize ===
| + | |
- | | + | |
- | Planner John logs in and see 3 new shipments that Mary created and he may authorize. See [[#Figure 8]]
| + | |
- | | + | |
- | === Use case. Planner John authorize shipments ===
| + | |
- | | + | |
- | Planner John rejects CT#... puts on hold CT#... and approve CT#... See Approved tab [[#Figure 9]], Hold tab [[#Figure 10]], Reject Tab [[#Figure 11]].
| + | |
- | | + | |
- | == Figures ==
| + | |
- | | + | |
- | === Figure 1 ===
| + | |
- | [[File:Shipper User for EA Dom and Jackel.JPG]]
| + | |
- | | + | |
- | === Figure 2 ===
| + | |
- | [[File:Planner User John at Arden Stamford.JPG]]
| + | |
- | | + | |
- | === Figure 3 ===
| + | |
- | [[File:CreatedCTListWithOutCT.JPG]]
| + | |
- | | + | |
- | === Figure 4 ===
| + | |
- | [[File:GeneralCreateAdd3Commo.JPG]]
| + | |
- | | + | |
- | === Figure 5 ===
| + | |
- | [[File:DisclaimerAndPreview.JPG]]
| + | |
- | | + | |
- | === Figure 6 ===
| + | |
- | [[File:ConfirmationWith3records.JPG]]
| + | |
- | | + | |
- | === Figure 7 ===
| + | |
- | [[File:NewTabShipper.JPG]]
| + | |
- | | + | |
- | === Figure 8 ===
| + | |
- | [[File:NewTabEM.JPG]]
| + | |
- | | + | |
- | === Figure 9 ===
| + | |
- | [[File:ApproveTabEM.JPG]]
| + | |
- | | + | |
- | === Figure 10 ===
| + | |
- | [[File:NewToHoldEM.JPG]]
| + | |
- | | + | |
- | === Figure 10a ===
| + | |
- | [[File:HoldTabEM.JPG]]
| + | |
- | | + | |
- | === Figure 11 ===
| + | |
- | [[File:RejectedTabEM.JPG]]
| + | |
- | | + | |
- | === Figure 12 ===
| + | |
This article describes design (solution) for Cybertrax ver 2.1 Client application a.k.a. Shipper Interface.