Log v2

From UG

(Difference between revisions)
Jump to: navigation, search
(Requirements)
(Requirements)
Line 3: Line 3:
== Requirements ==
== Requirements ==
-
In some cases loose ends are well known but could not be eliminated.
+
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.
Then there is at least need to monitor.

Revision as of 23:11, 30 September 2010


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

Personal tools