Log v2

From UG

(Difference between revisions)

Jump to: navigation, search

Revision as of 23:39, 2 August 2013

Info

THIS IS AN OLDER VERSION AND HAS BEEN DISCONTINUED
Latest version is here: Log

parent: 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://ct.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

History

2656: [EDI to TMS] bug: CT2_System_Log feature: Table 2 in Cont tab changes do not log properly

2677: [EDI to TMS] CT2_System_Log feature Change: Move "Shipment Import After Load Plan Msg Received" to TMS section instead of Ops

@@ Line 1: / Line 1: @@
 [[Category:CT2Misc]]
-== Parent Mantis ==
+== Info ==
-[http://mantis.jaguarfreight.com/mantis/view.php?id=2406 2406]
+<font color="red">
+* THIS IS AN OLDER VERSION AND HAS BEEN DISCONTINUED
+* Latest version is here: [[Log]]
+</font>
+parent: [http://mantis.jaguarfreight.com/mantis/view.php?id=2406 2406]
 == Requirements ==