Visibility Redesign
From UG
(→Requirements) |
(→Design Ideas) |
||
| Line 48: | Line 48: | ||
== Design Ideas == | == Design Ideas == | ||
| + | See Detailed Design. | ||
== Detailed Technical Design and Architecture == | == Detailed Technical Design and Architecture == | ||
== History == | == History == | ||
Revision as of 15:39, 15 November 2010
Contents |
About
This is a project.
Parent Mantis
0002553: [*11 Alex] (SA and BA) Visibility groups
Requirements
System re-design required in the area of Record Visibility to make it more flexible and convenient to use.
CT Record Visibility (definition). It is a set of criteria that allow or prohibit any given CT2 user to see (and potentially manage) any given CT2 shipment record.
Flexibility requirement. At the moment certain non trivial cases are hard or impossible to configure.
Convenience requirement. Management of visibility should be easy and fast.
Examples
Example 1.
Client Company A has users that may want to see more than only "their" company, however, they only need to see a "portion" of the other company based on some criteria (for example "only" ocean shipments from Europe).
Example 2.
Maticplast Users (possible choices):
- Client Maticplast
- as defined by E0
- From Maticplast "to COTY"
- shipper (maticplast) AND consignee (COTY)
- from Maticplast to "EA"
- shipper (maticplast) AND consignee (Elizabeth Arden, CEI, Kolmar, Evergreen etc)
- From "Maticplast" (to "client")
- shipper (maticplast) AND E0 Client "Elizabeth Arden"
- From "Maticplast" (to all)
- shipper (maticplast)
Note: (maticplast) could be multiple addresses (one in Rome, one in Milan, one in Naples)
Design Ideas
See Detailed Design.
