Visibility Redesign

From UG

Revision as of 16:26, 15 November 2010 by Alex (Talk | contribs)
Jump to: navigation, search


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.

Detailed Technical Design and Architecture

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

Main Idea

To define 2 step process to create visibility:

  • create visibility group (VG) with unique ID, Name and criteria
  • map one or more users to one or more selected VGs

VG criteria should include multiple filters to add flexibility

VG criteria could be modified later which will affect all linked users.

History

Personal tools