Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0030619 | Openbravo ERP | 09. Financial management | public | 2015-08-21 10:07 | 2015-09-28 13:19 |
|
Reporter | maite | |
Assigned To | Triage Omni OMS | |
Priority | urgent | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | 3.0PR16Q1 | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | vmromanos |
OBNetwork customer | OBPS |
Web browser | |
Modules | Core |
Support ticket | 37973 |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0030619: Error "java.text.ParseException: Unparseable date: "null" received when running Add Payment process from a copied window |
Description | Error "java.text.ParseException: Unparseable date: "null" received when running Add Payment process from a copied window |
Steps To Reproduce | 1. As System Administrator, access Windows, Tabs and Fields and create new record. Run process "Copy window tabs" selecting Sales Invoice window
2. As System Administrator, access Menu and create new records with type= window and referencing previous window
3. Logout and login
4. Access copied window and select an invoice with Payment Complete=No
5. Run Add Payment process and error "org.openbravo.base.exception.OBException: java.text.ParseException: Unparseable date: "null"" will be raised |
Proposed Solution | Handle the error, (the DefaultsProcessActionHandler class looks a good choice), showing the correct message, including a link to the documentation where the creation of the missing classes should be explained. And finally the Add Payment pop-up should be closed automatically in order to avoid further problems. |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0029035 | | closed | inigosanchez | Process definition containing parameters defined as "window", should automatically inherit permissions |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2015-08-21 10:07 | maite | New Issue | |
2015-08-21 10:07 | maite | Assigned To | => platform |
2015-08-21 10:07 | maite | OBNetwork customer | => Yes |
2015-08-21 10:07 | maite | Modules | => Core |
2015-08-21 10:07 | maite | Support ticket | => 37973 |
2015-08-21 10:07 | maite | Resolution time | => 1443045600 |
2015-08-21 10:07 | maite | Triggers an Emergency Pack | => No |
2015-08-21 10:08 | maite | Relationship added | related to 0029035 |
2015-08-21 10:08 | maite | Issue Monitored: networkb | |
2015-08-24 15:17 | caristu | Note Added: 0079641 | |
2015-08-24 15:21 | caristu | Assigned To | platform => Triage Finance |
2015-08-24 15:21 | caristu | Category | A. Platform => 09. Financial management |
2015-08-24 15:21 | caristu | Proposed Solution updated | |
2015-08-24 15:22 | caristu | Note Edited: 0079641 | bug_revision_view_page.php?bugnote_id=0079641#r9261 |
2015-08-25 11:38 | vmromanos | Note Added: 0079689 | |
2015-08-25 11:38 | vmromanos | Severity | major => minor |
2015-08-31 14:31 | maite | Resolution time | 1443045600 => |
2015-08-31 14:42 | maite | Review Assigned To | => alostale |
2015-08-31 14:42 | maite | Resolution time | => 1443045600 |
2015-08-31 14:42 | maite | Status | new => feedback |
2015-09-02 10:12 | maite | Note Added: 0080013 | |
2015-09-02 10:12 | maite | Status | feedback => new |
2015-09-28 11:17 | vmromanos | Target Version | 3.0PR15Q4 => 3.0PR16Q1 |
2015-09-28 13:19 | vmromanos | Review Assigned To | alostale => vmromanos |
2015-09-28 13:19 | vmromanos | Note Added: 0080668 | |
2015-09-28 13:19 | vmromanos | Status | new => closed |
2015-09-28 13:19 | vmromanos | Resolution | open => no change required |
Notes |
|
(0079641)
|
caristu
|
2015-08-24 15:17
(edited on: 2015-08-24 15:22) |
|
Every window which makes use of the Add Payment window has its own classes to handle the default values and display logics of the Add Payment pop-up. For example, the Sales Invoice window makes use of the following classes: SalesInvoiceAddPaymentDefaultValues, SalesInvoiceAddPaymentDisplayLogics and SalesInvoiceAddPaymentReadOnlyLogics.
The problem here is that the newly created window does not have any of these handlers, causing the error.
To avoid this problem, these case error be handled, showing the proper message and pointing to the documentation where the creation of these classes should be explained.
|
|
|
|
Candidate to be rejected.
Temporary changed severity to minor, as this is a consequence of an external customization and not a problem in the Product.
The reporter has been informed about a way to develop a fix in his customization. |
|
|
(0080013)
|
maite
|
2015-09-02 10:12
|
|
cloned window containing Add Payment process is not working any more after upgrade the environment |
|
|
|
|