Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0038042 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
defect | [Modules] Advanced Warehouse Operations | minor | always | 2018-03-05 16:34 | 2018-03-26 15:59 | |||||||
Reporter | maarten1962 | View Status | public | |||||||||
Assigned To | dmiguelez | |||||||||||
Priority | urgent | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Regression date | ||||||||||||
Regression introduced by commit | ||||||||||||
Regression level | ||||||||||||
Review Assigned To | ||||||||||||
Regression introduced in release | ||||||||||||
Summary | 0038042: Warehouse Verbosity Report does not create Verbosity and screen-content can not be copied | |||||||||||
Description | When the report is [done] it refers to the verbosity log "Please check verbosity log". The verbosity config is active and set to lowest level of reporting. Still there is no output. | |||||||||||
Steps To Reproduce | Login to Al Accad production environment. Window Warehouse Configuration Check. Select just whse and just 1 or 2 checks and run. When finished there is no verbosity while there should be. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0103062) vmromanos (manager) 2018-03-07 13:50 |
Verbosity log is designed to show log about task generation (and confirmation when autoconfirm routing only). The reason is this window has several fields that only make sense in task generation, like Batch Of Tasks or Inventory Transaction Type. Besides there is a log cleanup background process that deletes records from this window on a regular basis. It's a bad idea to try to reuse this window for other purposes. On the other hand I may understand it could be interesting to store the log in the database, but in this case a new window "warehouse check configuration log" should be created for this purpose. For this issue my recommendation would be just to fix the message and, if required, to log a new feature request to implement this new log window. |
(0103510) maarten1962 (reporter) 2018-03-26 15:59 |
A button [Download to XLS] on the Warehouse Configuration Check would be OK. Remember that this functionality used to write Verbosity and someone changed that. Whatever the reason, the output should not be just on screen, there is just too big volume for that. |
Issue History | |||
Date Modified | Username | Field | Change |
2018-03-05 16:34 | maarten1962 | New Issue | |
2018-03-05 16:34 | maarten1962 | Assigned To | => dmiguelez |
2018-03-07 13:50 | vmromanos | Note Added: 0103062 | |
2018-03-07 13:50 | vmromanos | Severity | major => minor |
2018-03-26 15:59 | maarten1962 | Note Added: 0103510 | |
2022-09-06 17:18 | caristu | Category | Advance Warehouse Operations => Advanced Warehouse Operations |
Copyright © 2000 - 2009 MantisBT Group |