Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0030619Openbravo ERP09. Financial managementpublic2015-08-21 10:072015-09-28 13:19
maite 
Triage Omni OMS 
urgentminoralways
closedno change required 
5
 
3.0PR16Q1 
vmromanos
Core
No
0030619: Error "java.text.ParseException: Unparseable date: "null" received when running Add Payment process from a copied window
Error "java.text.ParseException: Unparseable date: "null" received when running Add Payment process from a copied window
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
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.
No tags attached.
related to defect 0029035 closed inigosanchez Process definition containing parameters defined as "window", should automatically inherit permissions 
Issue History
2015-08-21 10:07maiteNew Issue
2015-08-21 10:07maiteAssigned To => platform
2015-08-21 10:07maiteModules => Core
2015-08-21 10:07maiteResolution time => 1443045600
2015-08-21 10:07maiteTriggers an Emergency Pack => No
2015-08-21 10:08maiteRelationship addedrelated to 0029035
2015-08-21 10:08maiteIssue Monitored: networkb
2015-08-24 15:17caristuNote Added: 0079641
2015-08-24 15:21caristuAssigned Toplatform => Triage Finance
2015-08-24 15:21caristuCategoryA. Platform => 09. Financial management
2015-08-24 15:21caristuProposed Solution updated
2015-08-24 15:22caristuNote Edited: 0079641bug_revision_view_page.php?bugnote_id=0079641#r9261
2015-08-25 11:38vmromanosNote Added: 0079689
2015-08-25 11:38vmromanosSeveritymajor => minor
2015-08-31 14:31maiteResolution time1443045600 =>
2015-08-31 14:42maiteReview Assigned To => alostale
2015-08-31 14:42maiteResolution time => 1443045600
2015-08-31 14:42maiteStatusnew => feedback
2015-09-02 10:12maiteNote Added: 0080013
2015-09-02 10:12maiteStatusfeedback => new
2015-09-28 11:17vmromanosTarget Version3.0PR15Q4 => 3.0PR16Q1
2015-09-28 13:19vmromanosReview Assigned Toalostale => vmromanos
2015-09-28 13:19vmromanosNote Added: 0080668
2015-09-28 13:19vmromanosStatusnew => closed
2015-09-28 13:19vmromanosResolutionopen => 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.

(0079689)
vmromanos   
2015-08-25 11:38   
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
(0080668)
vmromanos   
2015-09-28 13:19   
This is a consequence of the usage of the new Process Definition framework on Java for default values, display logic and read only logic.

Documented in release notes: http://wiki.openbravo.com/wiki/Release_Notes/3.0PR14Q3#Known_issues [^]