Log v2

From UG

Revision as of 13:08, 5 October 2010 (edit) Andrei (Talk | contribs) m (→Cases: added link to "Shipment Import" and "Load Plan") ← Older edit		Revision as of 14:11, 5 October 2010 (edit) (undo) Alex (Talk | contribs) (→Cases) Newer edit →
Line 35:		Line 35:
	=== Cases ===		=== Cases ===
-	* '''UC 101:''' Editing Shipment data on CT side after [[Shipment Import]]
-	:* '''UC 101A:''' Change of Shipment data on CT2 side after [[Shipment Import]] '''before''' [[Load Plan]] Message received
-	:* '''UC 101B:''' Change of Shipment data on CT2 side after [[Shipment Import]] '''after''' [[Load Plan]] Message received
-	* '''UC 102:''' Editing Shipment data on TMS side after [[Shipment Import]]
-	* '''UC 103:''' One Commodity line with both loose and plts will translate into 2 line items on Descartes side
-	Detailed description see here - http://mantis.jaguarfreight.com/wiki/Use_Cases_for_EDI_to_TMS#Various_Use_Cases_100	+	==== 1 ====
		+
		+	Message: "Operator <login info> Changed Shipment data on CT2 side after Shipment Import after Load Plan Message received. Fields changed: ....<CT#><field, value from, value to> ... ". Message priority = high.
	=== Figures ===		=== Figures ===
	==== Figure1. CT2 System Log ====		==== Figure1. CT2 System Log ====
	[[File:CT2 System Log.gif]]		[[File:CT2 System Log.gif]]

---

Revision as of 14:11, 5 October 2010

Contents 1 Requirements 2 Design 2.1 Summary 2.2 Columns 2.3 Cases 2.3.1 1 2.4 Figures 2.4.1 Figure1. CT2 System Log

Requirements

In some cases loose ends are well known but could not be eliminated for political / other reasons.

Then there is at least need to monitor.

This is one of the reasons for "CT2 System Log".

Event could be posted with attributes:

• priority: high/med/low
• date
• summary

Table should be search able and sortable with paging.

Example of use: http://mantis.jaguarfreight.com/wiki/Use_Cases_for_EDI_to_TMS#UC_101A_Change_of_Shipment_data_on_CT2_side_after_Shipment_Import_before_Load_Plan_Message_received

Design

Summary

CT2 System Log is a summary table which reflects some specific changes in the CTs. These changes happen in the cases specified in #Cases section.

CT2 System Log is a standard CT2 table with sorting and paging features and located on CT2 homepage.

Columns

• Priority
• Date
• User
• Use Case ID
• Summary
• Details

Cases

1

Message: "Operator <login info> Changed Shipment data on CT2 side after Shipment Import after Load Plan Message received. Fields changed: ....<CT#><field, value from, value to> ... ". Message priority = high.

Figures

Figure1. CT2 System Log