Openbravo Issue Tracking System - Modules
However, this is a problem in some scenarios.
Example. There is a Task, and the user confirms the Task with 0 quantity and selects the option to do a Delta Different.
If there is no Stock in the system, the Delta Task raises an exception and the original Task remains not confirmed.
But, since it is included in the "Errors while confirming" Table, it is not shown to the user again, so the user can not perform further actions against this Task.
To solve this problem, there should be a differentiation between errors that happens due to a software bug or an unexpected error and the controlled exceptions, like the inability to generate a Delta Task due to the lack of Stock
If the error is raised due to a software bug or an unexpected situation, it should be managed as it is done now. A new entry in the "Errors while confirming Task" Table is created and the Task is no longer visible for the user. The manager should manage this situation afterwards.
If the error is raised due to a controlled situation, what should happen is:
- The error is not stored into the "Errors while confirming Task" Table
- The error is stored in a new Tab under the Task Window that could be named "Warnings while processing"
- This Tab will work as a log of all the errors that had happened while confirming, so information about user and time is a must
- The Task should be shown to the user
- It should be presented in a different color or with some icon for the user to understand that the Task have had errors while confirming
- A message should be shown with the last error that has happened
However, this is a problem in some scenarios.
Example. There is a Task, and the user confirms the Task with 0 quantity and selects the option to do a Delta Different.
If there is no Stock in the system, the Delta Task raises an exception and the original Task remains not confirmed.
But, since it is included in the "Errors while confirming" Table, it is not shown to the user again, so the user can not perform further actions against this Task.
To solve this problem, there should be a differentiation between errors that happens due to a software bug or an unexpected error and the controlled exceptions, like the inability to generate a Delta Task due to the lack of Stock
If the error is raised due to a software bug or an unexpected situation, it should be managed as it is done now. A new entry in the "Errors while confirming Task" Table is created and the Task is no longer visible for the user. The manager should manage this situation afterwards.
If the error is raised due to a controlled situation, what should happen is:
- The error is not stored into the "Errors while confirming Task" Table
- The error is stored in a new Tab under the Task Window that could be named "Warnings while processing"
- This Tab will work as a log of all the errors that had happened while confirming, so information about user and time is a must
- The Task should be shown to the user
- It should be presented in a different color or with some icon for the user to understand that the Task have had errors while confirming
- A message should be shown with the last error that has happened
Icon suggestions to show on Task.png (101,497) 2018-04-18 10:54https://issues.openbravo.com/file_download.php?file_id=11746&type=bug