Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0004513 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| feature request | [Openbravo ERP] 00. Application dictionary | minor | always | 2008-07-26 12:42 | 2009-05-22 19:26 | |||
| Reporter | rafaroda | View Status | public | |||||
| Assigned To | iciordia | |||||||
| Priority | normal | Resolution | duplicate | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Linux 32 bit | Database | PostgreSQL | Java version | 1.5 | |||
| OS Version | Ubuntu 7.10 | Database version | 8.3 | Ant version | 1.7 | |||
| Product Version | pi | SCM revision | 5996 | |||||
| Review Assigned To | ||||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0004513: Fields relations within Application Dictionary | |||||||
| Description | It would be useful to be able to define conditions/relations between fields in order to avoid wrong data insertion. For instance, in a Project, if the Ending Date is lower than the Starting Date a message should display (as it is displaying for wrong dates) and one should not be able to save this record. The same could be implemented for: * Quantities that have to be one bigger or equal to another. * Quantities that are a function of others (Field 3 = Field 1 * Field 2) At the end, it would allow to implement simple callout-like/trigger-like logics without having to code. | |||||||
| Steps To Reproduce | 1) Go to Project & Service Management || Transactions || Multiphase Project || Project >> Project Phase 2) Set a Starting Date 3) Set an Ending Date lower than Starting Date No check is done. | |||||||
| Proposed Solution | In Application Dictionary, at a field level, add a tab that permits to register relationship checks/calculations between fields. Fields related could be in the same tab or in different tabs. | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0010313) pjuvara (reporter) 2008-11-16 18:08 |
Part of this request is duplicate of 391. For others, I am not sure that they are essential. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-07-26 12:42 | rafaroda | New Issue | |
| 2008-07-26 12:42 | rafaroda | Assigned To | => cromero |
| 2008-07-26 12:42 | rafaroda | sf_bug_id | 0 => 2028635 |
| 2008-07-26 13:15 | rafaroda | Summary | Fields relations check within Application Dictionary => Fields relations within Application Dictionary |
| 2008-07-26 13:15 | rafaroda | Description Updated | |
| 2008-07-26 13:15 | rafaroda | Steps to Reproduce Updated | |
| 2008-07-26 14:16 | rafaroda | Relationship added | blocks 0004514 |
| 2008-11-10 13:10 | cromero | Assigned To | cromero => pjuvara |
| 2008-11-16 18:08 | pjuvara | Regression testing | => No |
| 2008-11-16 18:08 | pjuvara | Relationship added | duplicate of 0000391 |
| 2008-11-16 18:08 | pjuvara | Status | new => closed |
| 2008-11-16 18:08 | pjuvara | Note Added: 0010313 | |
| 2008-11-16 18:08 | pjuvara | Duplicate ID | 0 => 391 |
| 2008-11-16 18:08 | pjuvara | Resolution | open => duplicate |
| 2008-11-16 18:09 | pjuvara | Relationship deleted | blocks 0004514 |
| 2009-05-22 19:26 | pjuvara | Assigned To | pjuvara => iciordia |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |