Log v2

From UG

Revision as of 14:15, 5 October 2010 (edit) Alex (Talk | contribs) (→Event 1) ← Older edit		Revision as of 16:01, 5 October 2010 (edit) (undo) Andrei (Talk | contribs) (→Columns) Newer edit →
Line 29:		Line 29:
	* Priority		* Priority
	* Date		* Date
-	* User	+	* Jaguar User / Office
-	* Use Case ID	+	* CT#
		+	* Event
	* Summary		* Summary
	* Details		* Details

---

Revision as of 16:01, 5 October 2010

Contents 1 Requirements 2 Design 2.1 Summary 2.2 Columns 2.3 Events 2.3.1 Event 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
• Jaguar User / Office
• CT#
• Event
• Summary
• Details

Events

Event 1

See d) in Use Cases for EDI to TMS#UC 101B Change of Shipment data on CT2 side after Shipment Import after Load Plan Message received

Figures

Figure1. CT2 System Log