Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0028390 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Openbravo ERP] 09. Financial management | minor | have not tried | 2014-12-11 16:56 | 2014-12-15 14:20 | |||
Reporter | plujan | View Status | public | |||||
Assigned To | aferraz | |||||||
Priority | normal | Resolution | no change required | Fixed in Version | ||||
Status | closed | 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 | pi | SCM revision | ||||||
Review Assigned To | Sandrahuguet | |||||||
Web browser | ||||||||
Modules | Core | |||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0028390: When saving a Financial Account Transaction leaving Payment field blank, an error is logged | |||||||
Description | New Financial Account Transaction window has Payment and GL Item fields as non mandatory, since a business rule checks that at least one of them is filled. If the form is filled leaving those fields blank, the correct message is displayed asking the user to fill one. The problem is that at the same time an error is added to the log. | |||||||
Steps To Reproduce | 1. Enter as QA Admin user 2. Go to Financial Account window 3. Select Spanish Cashbook record 4. Move to Transaction tab 5. Click New to create a new record and fill all the mandatory (yellow background) fields. Be sure that Payment and GL Item fields are both blank. 6. Save the record. You get the expected message "Saving failed. This transaction type must define either a Payment or a G/L Item" 7. Check the log, an exception has been logged. ERROR org.openbravo.base.exception.OBException - @APRM_INVALID_TRANSACTION@ | |||||||
Proposed Solution | Since the error has been properly managed by the GUI by not letting the user save the record, there is not need to get an error in the log. If the info is required to get more detail, I'd suggest using an INFO instead. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0072511) aferraz (manager) 2014-12-15 14:20 |
Showing the error in the GUI and also in the log is the normal behavior as it is the same than in other windows of Openbravo. |
Issue History | |||
Date Modified | Username | Field | Change |
2014-12-11 16:56 | plujan | New Issue | |
2014-12-11 16:56 | plujan | Assigned To | => Sandrahuguet |
2014-12-11 16:56 | plujan | Modules | => Core |
2014-12-11 16:56 | plujan | Triggers an Emergency Pack | => No |
2014-12-15 14:15 | aferraz | Assigned To | Sandrahuguet => aferraz |
2014-12-15 14:20 | aferraz | Review Assigned To | => Sandrahuguet |
2014-12-15 14:20 | aferraz | Note Added: 0072511 | |
2014-12-15 14:20 | aferraz | Status | new => closed |
2014-12-15 14:20 | aferraz | Resolution | open => no change required |
Copyright © 2000 - 2009 MantisBT Group |