Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0011054 | Openbravo ERP | 00. Application dictionary | public | 2009-10-20 16:51 | 2011-11-28 18:39 |
|
| Reporter | galderromo | |
| Assigned To | iciordia | |
| Priority | high | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | |
| Platform | | OS | 20 | OS Version | Gentoo 2.6.24 |
| 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 | 0011054: Mandatory fields should be based in logic rules |
| Description | Actually if a field is mandatory or not is defined on ad_column. Usually happens more than a window-tabs-fields are based on the same tables-columns.
On this situation, oftenly being mandatory or not can dependen on the field instead of the being on the column. And this is not supported.
Having a new functionality to manage this situation, based on "mandatority logic rules" will be a big step forward. |
| Steps To Reproduce | |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-10-20 16:51 | galderromo | New Issue | |
| 2009-10-20 16:51 | galderromo | Assigned To | => rafaroda |
| 2009-10-22 12:58 | rafaroda | Assigned To | rafaroda => iciordia |
| 2010-04-29 10:59 | andreaferaco | Issue Monitored: andreaferaco | |
| 2010-04-29 11:01 | andreaferaco | Note Added: 0026796 | |
| 2011-11-28 18:39 | RafaelCruz | Issue Monitored: RafaelCruz | |