Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0011054 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| feature request | [Openbravo ERP] 00. Application dictionary | minor | always | 2009-10-20 16:51 | 2011-11-28 18:39 | |||||||
| Reporter | galderromo | View Status | public | |||||||||
| Assigned To | iciordia | |||||||||||
| Priority | high | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Linux 32 bit | Database | Oracle | Java version | 1.5.0_15 | |||||||
| OS Version | Gentoo 2.6.24 | Database version | XE | Ant version | 1.7 | |||||||
| Product Version | SCM revision | |||||||||||
| Merge Request Status | ||||||||||||
| Review Assigned To | ||||||||||||
| OBNetwork customer | No | |||||||||||
| 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. | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0026796) andreaferaco (viewer) 2010-04-29 11:01 |
We are interested on this feature. I mean we would have been expected a sort of mandatory logic for a field which is based on an approach similar to what used for display logic, that is to set a field as mandatory or not at run-time according to the evaluation of a boolean expression. |
|
Notes |
|
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-20 16:51 | galderromo | OBNetwork customer | => No |
| 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 | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |