Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0019871 | Openbravo ERP | A. Platform | public | 2012-02-24 13:40 | 2022-02-01 08:08 |
| Reporter | marvintm | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | acknowledged | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| 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 | 0019871: Auxiliary input naming rules should be reconsidered | ||||
| Description | Currently, auxiliary input naming rules are too strict. As an auxiliary input is a component very similar to columns, its naming rules should be basically identical. Therefore: - When an auxiliary input is related to a tab belonging to a different module, it is correct to require it to start with the dbprefix of its module, to avoid collissions. - However, when an auxiliary input is related to a tab belonging to the same module, it is not necessary for it to have a special name, for the same reason a column of a table which belongs to the same module doesn't need any special naming rule. Moreover, we could be even more aggressive, and remove all naming rules requirement, and apply auxiliary inputs in a module-dependency-ordered way. This design limitation has already caused a regression in customer environments: https://issues.openbravo.com/view.php?id=19857 [^] | ||||
| Steps To Reproduce | Attempt to create a new auxiliary input in a new tab in a module. You will be forced to choose a name which starts with the dbprefix of the module, regardless of the fact that the tab and the auxiliary input belong to the same module. | ||||
| Proposed Solution | The two proposed solutions have been stated in the description of the issue. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2012-02-24 13:40 | marvintm | New Issue | |||
| 2012-02-24 13:40 | marvintm | Assigned To | => alostale | ||
| 2012-02-24 13:40 | marvintm | Modules | => Core | ||
| 2012-09-24 20:50 | AugustoMauch | Note Added: 0052391 | |||
| 2012-09-24 20:50 | AugustoMauch | Status | new => scheduled | ||
| 2017-03-31 14:36 | alostale | Status | scheduled => acknowledged | ||
| 2017-04-10 14:33 | alostale | Assigned To | alostale => platform | ||
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base | ||
| Notes | |||||
|
|
|||||
|
|
||||