Log

From UG

Revision as of 13:37, 17 October 2010 (edit) Andrei (Talk | contribs) (→Columns) ← Older edit		Revision as of 13:43, 17 October 2010 (edit) (undo) Andrei (Talk | contribs) m (→Columns: changed list of types of events) Newer edit →
Line 151:		Line 151:
	:* Name of Jaguar User who made changes (and User's Office).		:* Name of Jaguar User who made changes (and User's Office).
	* '''Event'''		* '''Event'''
-	:* Type of happened change: ''{ Create, Remove, Edit }''.	+	:* Type of happened change: ''{ Add, Remove, Edit, Archive, Restore }''.
-	:: ''What about Archive and Restore?'' --[[User:Andrei|Andrei]] 09:37, 17 October 2010 (EDT)	+
	* '''Component'''		* '''Component'''
	:* Name of the [[#Components |component]] where change happened.		:* Name of the [[#Components |component]] where change happened.

---

Revision as of 13:43, 17 October 2010

Contents 1 General Info and Scope 1.1 Scope 1.2 Related articles 2 Business Requirements 3 Design 3.1 Summary 3.2 Components 3.3 Sub-Components 3.4 Columns 4 Figures 4.1 Figure 0. Main Menu item 4.2 Figure 1. Admin Update Log 5 History

General Info and Scope

• Classified As: (small) (large) component / common feature / misc
• Parent Mantis: 2397

Scope

This is a CRUD component for CT2 Admin Update Log.

Related articles

Business Requirements

(copied from mantis #2397)

All changes to Admin should be reflected in special Log.
Info to show: When change happened, Who changed, What was changed, Admin Component where change happened
Easy way to search/filter by fields above.
Discuss w/ developer
Most important: Jag/Non-Jag users, Users Access Admin
Note: we have similar task for Acc 

Design

Summary

Admin Update Log should reflected all changes in Admin part of CT2.

It is available from the main menu on the next path: "Admin -> Admin Update Log". See Figure 0.

This feature displayed in the table form which contains the next details of Admin changes:

1) When change happened,

2) Who is made changes,

3) What was changed,

4) Admin Component (and Sub-Component) where change happened.

Admin Update log should provide a search feature. All columns of Admin Update log should have an able to a sorting.

Example of Admin Update Log see on Figure 1.

Components

• Address Book
• Client Companies
• Create CT Admin
• Users and Offices
• Geography
• Transportation
• Carriers
• Automated Estimated Delivery Dates
• Users Access Admin
• Client App Admin
• Shipment Invoices Recovery

Sub-Components

Address Book

• Company-City List
• Transportation
• Vendors
• Bill To Parties

Client Companies

• Client Companies
• Client Companies Groups
• Credit Limits
• Credit Terms
• Credit Statuses

Create CT Admin

• Numbers
• CT1 vs CT2 Client Companies

Users and Offices

• Offices
• Jaguar Users Groups
• Jaguar Users
• Non-Jaguar Users

Geography

• Regions
• Countries
• Airports
• Port/Terminals
• Busiest Port/Terminals

Transportation

• Shipping Terms
• Default Authorization Methods
• Move Types/HBLs
• Container Sizes
• Container Types
• Customs Statuses
• FDA Statuses
• Packaging Pallet Types
• Delivery Date Types
• PO Issued By

Carriers

• Airlines
• Steamshiplines

Automated Estimated Delivery Dates

• Air
• FCL AW
• FCL MLB
• LCL AW
• LCL MLB

Users Access Admin

• Basic Ops
• Super Ops
• Basic Acc
• Super Acc
• Management
• Sales
• Blank1
• Blank2

Fields:

- Ops Home

- List CTs

- List Ms

- Create CT

- Create M

- Admin Home

- Admin.Users

- Admin.Geography

- Admin.Transportation

- Admin.Address Book

- Admin.Client Companies

- Admin.Carriers

- Reports Home

- Acc Home

- CT Rights Administration

- Delete saved documents

- Edit/Delete Comments/Query

- TMS

Client App Admin

• Manage RSS News Feeds
• Testimonials
• Mobile Providers
• BCC List
• TMS

Shipment Invoices Recovery

Columns

• Date

• Date when change happened. Displayed in standard CT2 date format.

• Jaguar User / Office

• Name of Jaguar User who made changes (and User's Office).

• Event

• Type of happened change: { Add, Remove, Edit, Archive, Restore }.

• Component

• Name of the component where change happened.

• Sub-Component

• Name of the sub-component where change happened.

• Field

• Name of the field what was changed.

• Change

• Old and new values of changed fields in format old value => new value.

Figures

Figure 0. Main Menu item

Figure 1. Admin Update Log

History