Log v2
From UG
(Difference between revisions)
(→Figures) |
(→Requirements) |
||
Line 20: | Line 20: | ||
Table should be search able and sortable with paging. | Table should be search able and sortable with paging. | ||
- | Example of use: http:// | + | 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 == | == Design == |
Revision as of 22:05, 19 January 2011
Contents |
Parent Mantis
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.
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
Figures
Figure1. CT2 System Log
or