Log v2

From UG

Revision as of 18:19, 16 October 2010 (edit) Alex (Talk | contribs) (→Summary) ← Older edit		Revision as of 18:03, 11 January 2011 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 1:		Line 1:
-	[[Category:CT2 Portals Architecture]]	+	[[Category:CT2Misc]]
	== Parent Mantis ==		== Parent Mantis ==

---

Revision as of 18:03, 11 January 2011

Contents 1 Parent Mantis 2 Requirements 3 Design 3.1 Summary 3.2 Columns 3.3 Events 3.3.1 Event 1 3.4 Figures 3.4.1 Figure1. CT2 System Log

Parent Mantis

2406

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 #Events section.

CT2 System Log is a standard CT2 table with sorting and paging features and located under Admin menu.

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

or