Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0008551 | Openbravo ERP | A. Platform | public | 2009-04-12 13:24 | 2011-10-28 14:22 |
|
| Reporter | roklenardic | |
| Assigned To | alostale | |
| Priority | low | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | |
| Platform | | OS | 20 | OS Version | Ubuntu 9.04 |
| Product Version | 2.50beta | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0008551: Callout name must not contain spaces |
| Description | If a callout name in window Application Dictionary || Setup || Callout contains space then the generated code looks like
function calloutHotel Stay Final Sum Calculation(changedField) {
submitCommandFormParameter('DEFAULT', frmMain.inpLastFieldChanged, changedField, false, null, '../com.mycompany.hotel.ad_callouts/HotelStayFinalSumCalculation.html', 'hiddenFrame', null, null, true);
return true;
}
Obviously, java function definition cannot contain spaces so the callout not only does not work but corrupts the functionality of the entire tab that contains it. |
| Steps To Reproduce | Introduce a constrain that prevents saving callout names with spaces or change wad so that it removes spaces of the callout when it generates the callout function. |
| Proposed Solution | |
| Additional Information | |
| Tags | dev-platform-quick-wins |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-04-12 13:24 | roklenardic | New Issue | |
| 2009-04-12 13:24 | roklenardic | Assigned To | => rafaroda |
| 2009-04-12 13:24 | roklenardic | Regression testing | => No |
| 2009-04-21 18:58 | joan | Note Added: 0015498 | |
| 2009-04-21 18:59 | joan | Issue Monitored: joan | |
| 2009-04-23 09:27 | psarobe | Priority | normal => low |
| 2009-04-23 09:27 | psarobe | Status | new => scheduled |
| 2009-04-23 09:46 | rafaroda | Assigned To | rafaroda => alostale |
| 2010-09-07 10:56 | rafaroda | Tag Attached: dev-platform-quick-wins | |
| 2010-09-07 10:56 | rafaroda | Issue Monitored: rafaroda | |
| 2011-10-28 12:14 | psarobe | Note Added: 0042215 | |
| 2011-10-28 12:14 | psarobe | Status | scheduled => closed |
| 2011-10-28 12:14 | psarobe | Resolution | open => no change required |
| 2011-10-28 14:22 | roklenardic | Note Added: 0042260 | |
|
Notes |
|
|
(0015498)
|
|
joan
|
|
2009-04-21 18:58
|
|
2.50 seams to have the same behavoir also with lists definitions. If i create a List named Historial Números de Serie Work Effort. The compilation returns
/ob250/src-gen/org/openbravo/model/materialmgmt/transaction/ProductionTransaction.java:364: > expected
public void setHistorialNmerosDeSerieWorkEffortList(java.util.List<org.itae.Historial Números de Serie Work Effort> historialNmerosDeSerieWorkEffortList) {
And more errors about it.
Seams to dont like accents and spaces |
|
|
|
|
Openbravo provides community support only for the latest Openbravo version, which is Openbravo 3. This version has significantly improved financial flow, filtering, performance, etc and this issue is not present there. Upgrade path from Openbravo 2.50 to latest Openbravo version is available so we recommend to upgrade your instance to get this issue fixed.
Life cycle guarantee (backporting bug fixes to the previos to latest releases (Openbravo 2.40, 2.50)) is available for Professional Edition subscribers only. Please register your ticket through Openbravo Support Portal (http://support.openbravo.com/ [^]) if you have valid Professional subscription.
You can find more details about our Support policy in the following blog post
http://paolojuvara.blogspot.com/2009/12/maintenance-policy-for-openbravo-250.html [^] |
|
|
|
|
|
Pablo, this problem persists in 3.0 and is a design flaw. |
|