Visibility Redesign
From UG
Contents |
About
This is a project.
!!! See detailed designs / screens in history !!!!
Parent Mantis
0002553:[Visibility groups] Implement this
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. This should be resolved.
Convenience requirement. Management of visibility should be easy and fast.
Examples
Example 1.
Client Company A (E0 field on CT record) 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
SA Notes
Visibility criteria
In order for user X to see CT record#Y specific Visibility criteria should be satisfied.
Visibility criteria is a logical condition (Database Query String) expressed in terms of constraints on values of specific CT fields. It is similar to defining some filters before generating report.
Example.
Business requirement:
- User A should only see shipments from Shipper "Multiplast" to Consignee "COTY" or Consignee "Kolmar".
To satisfy this requirement Visibility criteria should be:
- (Ct#Shipper = "Multiplast" AND Ct#Consignee = "COTY" ) OR
- (Ct#Shipper = "Multiplast" AND Ct#Consignee = "Kolmar")
3 ways to define Visibility criteria for a user
I see 3 ways to define Visibility criteria for a user. All or just some could must be implemented.
- Through User Profile. Visibility criteria could be defined right in the individual user profile.
- For a group of users. Visibility Criteria could be defined for a group of users. First, group of users would be selected based on some set filters (user object attributes) and then Visibility Criteria could be applied to them.
- Through Visibility Templates a.k.a. Visibility Groups. Visibility Criteria could be saved as a Visibility Template so that later it could be used to apply to other users with the same visibility. Visibility Template should have Name defined by user and unique Id generated by System.
Scope
Visibility Management for the following types of users is out of scope of this project:
- Jaguar users
- Non-Jaguar users with Shipper and Planner roles
Data Migration
After new model is deployed we need to make sure that existing visibility for existing users is preserved.
Version of spec with mockups
See [[1]]
