International Portal Solution

From UG

(Difference between revisions)
Jump to: navigation, search
(SOW 4)
(SOW 4)
Line 136: Line 136:
== SOW 4 ==
== SOW 4 ==
-
'''
+
'''0003395: [* IPortal] SOW 4'''  
-
0003395: [* IPortal] SOW 4'''  
+
-
Original list that was put on hold:
+
* 1) "Self serve":
 +
** ability by non-jag user to create CT
 +
** this CT would be available to jag operators immediately (bypassing "planning module")
 +
== Future SOWs ==
-
* Shipment List (merge code for all roles and make avail to jag user on Client)
 
-
* Shipment Editor rewrite (SOW: TBD)
+
* International Shipper / Planner for Arden - idea is the same as 1) but:
 +
** it is continuation of existing Shipper / Planner for Arden for Dom Trucking (MOT Air/Ocean have to be added)
 +
** has specific Arden requirements that will be known later
-
* Users (leftovers: Apply Actions; active/arc; etc)
 
-
* System Roles (make bold or other way to stand out in UI)
 
 +
Leftovers:
-
International Shipper / Planner functionality is important. Split into 2 phases:
+
* Shipment List (merge code for all roles and make avail to jag user on Client)
-
* 1) "Self serve":
+
* Shipment Editor rewrite (SOW: TBD)
-
** ability by non-jag user to create CT
+
-
** this CT would be available to jag operators immediately (bypassing "planning module")
+
-
* 2) International Shipper / Planner for Arden - idea is the same as 1) but:
+
* Users (leftovers: Apply Actions; active/arc; etc)
-
** it is continuation of existing Shipper / Planner for Arden for Dom Trucking (MOT Air/Ocean have to be added)
+
 
-
** has specific Arden requirements that will be known later
+
* System Roles (make bold or other way to stand out in UI)

Revision as of 00:15, 23 February 2012


Contents

Info

  • Related mantis#:
    • 0002629: [Intl Portal] ... <proj>
    • 0002892: [Intl Portal] Implement phase 1

Implementation plan

Tasks:

  • 1/Merge Client and Internal application (gradually) - 3139, ...
  • 2/Shipment visibility re-design:
    • specific filter combination to define visibility, not E0 field
    • apply visibility to all roles including Jag users
  • Features visibility re-design (access rights for each role)
  • 3/ser profiles/user lists:
    • Introduce Jag user profile (note: this is also under DR/KPI proj)
    • Create common user profile (all roles) (note: this is also under DR/KPI proj)
  • 4/Add config to comply with SaaS requirement (link to user/company visibility, link to proper EDI)
    • move all EDI/Integration options to separate menu (Descartes TMS, Descartes Air status, Trendset, future Rates provider, etc)
  • 5/Improve users management panel (filters, apply action to many users at the same time)
  • 6/Flex Reports:
    • next version of List CTs
    • next ver of other reps
  • 7/Add roles of Intern Shipper, Agent, Trucker
  • 8/Add flexible Planning/Approval framework

Related mantis:

  • 3139 (Homepage/Layout) Implement v2.0 // spr#8d
  • 2553: [*IPortal] (Visibility groups) Implement new version // SA phase


Phase 1

May-Jul Sprint

  1. Admin panel for Shipper Role.
    • Added Mode Of Transport list to Shipper profile in Admin Panel.
    • Added prototype of Shipment Field access rights Admin Panel
  2. Started implementation of flexible Shipment Editor. Shipment Editor should looks similar to Internal Application Shiment Editor
    • Implemented base set of field editors (Gen Tab)
    • Started Dims Table editor on Cont Tab of editor
  3. Shipment List for Shipper/Planner role
    • Created Mode of Transport column
    • Sorting and Filter by Mode of Transport feature
    • Creation, Cloning, Editing shipments of any Transport Mode allowed to Shipper

NOTE: currently all these features were implemented as prototype.

Jul-Aug Sprint (Plan)

  1. Shipment Editor
    • complete all MOT specific fields editors for Air and Ocean Transport Modes on Imp and Exp Tabs
    • Implement dynamic switching allowed fields according to current Shipper (Planner) field access rights

Aug-Sept Sprint (Plan)

  1. Planner Role
    • implement Field Access admin panel for Planner role
    • support Approval Process for any type of MOT
    • selecting MOT for shipments


TBD

Solution phase 1

Figures

Figure 1. Admin panel for Shipper Role.

File:AdminPanelForShipperRole.gif

Figure 2. Admin panel. Shipper Role edit window.

File:AdminPanelShipperRoleWindow.gif

Figure 3. Admin panel. Shipment Field access rights window.

File:AdminPanelShipmentFieldAccess.gif

Figure 4. Shipment List for Shipper role.

File:ShipmentListForShipper.gif

Figure 5. Client Shipment Editor. Gen Tab.

File:ClientEditorGenTab.gif

Figure 6. Client Shipment Editor. Cont Tab.

File:ClientEditorContTab.gif

Phase 2

Users access levels and security framework

mantis: 0002971: [Intl Portal] (ph2) User's access permissions (UAP) Core (Core functionality and Admin Console)

  • user authentication
  • hiding/showing certain panels or menu options based on specific user type (client vs jaguar user for example)
  • currently we show restricted options, and show error pop-up. Instead we need to hide them based on user role/type.

User role and user type are closely related.

Jaguar role has these types: Basic Ops, Super Ops, Management, etc.

Phase 2 Implementation Notes and User Guide

see Security_Framework_/_User_Access#User_Guide

Phase 3

New Shipment Editor

The task it to create flexible and optimized shipment editor on Client App. This editor should:

  • support all the functionality that exists for shipment editor on Internal App
  • be "optimized": faster, cleaner code
  • support all new and old roles: Agent, International Shipper, Planner, Trucker, Jaguar user
  • support idea of "flexible field access" (each field can be configured to be R/W based on role)

Mantis:

  • 0003085: [Intl Portal] (ph3) Shipment Editor. Cont Tab. Dimension table.
  • 0003086: [Intl Portal] (ph3) Shipment Editor. Imp/Exp tabs. MOT: Air
  • 0003087: [Intl Portal] (ph3) Shipment Editor. Imp/Exp tabs. MOT: Ocean

Redesign user lists and user profiles

See Users#Feature Set 2

SOW 4

0003395: [* IPortal] SOW 4

  • 1) "Self serve":
    • ability by non-jag user to create CT
    • this CT would be available to jag operators immediately (bypassing "planning module")

Future SOWs

  • International Shipper / Planner for Arden - idea is the same as 1) but:
    • it is continuation of existing Shipper / Planner for Arden for Dom Trucking (MOT Air/Ocean have to be added)
    • has specific Arden requirements that will be known later


Leftovers:


  • Shipment List (merge code for all roles and make avail to jag user on Client)
  • Shipment Editor rewrite (SOW: TBD)
  • Users (leftovers: Apply Actions; active/arc; etc)
  • System Roles (make bold or other way to stand out in UI)
Personal tools