Log v2
From UG
(Difference between revisions)
(→Cases) |
(→Design) |
||
| Line 34: | Line 34: | ||
* Details | * Details | ||
| - | === | + | === Events === |
| - | ==== 1 ==== | + | ==== Event 1 ==== |
| - | + | See d) in [[UC 101B Change of Shipment data on CT2 side after Shipment Import after Load Plan Message received]] | |
| - | + | ||
=== Figures === | === Figures === | ||
==== Figure1. CT2 System Log ==== | ==== Figure1. CT2 System Log ==== | ||
[[File:CT2 System Log.gif]] | [[File:CT2 System Log.gif]] | ||
Revision as of 14:14, 5 October 2010
Contents |
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 #Cases section.
CT2 System Log is a standard CT2 table with sorting and paging features and located on CT2 homepage.
Columns
- Priority
- Date
- User
- Use Case ID
- Summary
- Details
Events
Event 1
See d) in UC 101B Change of Shipment data on CT2 side after Shipment Import after Load Plan Message received
Figures
Figure1. CT2 System Log
