Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0028340 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Openbravo ERP] A. Platform | minor | always | 2014-12-02 23:16 | 2022-02-01 08:08 | |||||||
| Reporter | jecharri | View Status | public | |||||||||
| Assigned To | Triage Platform Base | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| 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 | 0028340: The HQL Where clause in the selectors is not refreshing the current value | |||||||||||
| Description | The HQL Where clause in the selectors is not refreshing the current value. If you have a field that has OBUISEL selector reference and this this selector has a where clause depending in another value, if you change the value of this field the value of column with OBUISEL selector is not changeg | |||||||||||
| Steps To Reproduce | -Install attached module -Login as System -Go to references window and change the "HQL Where clause" of "products" reference to e.active='Y' AND e.isGeneric='N' AND e.productCategory.id=@inpmProductCategoryId@ -Login with admin role and go to selector window -Select a product -Verify that if you change the product category the product field is not updated and continue having a wrong value | |||||||||||
| Proposed Solution | I think that HQL Where clause should work as validations because it is not possible to assign a validation to one column that it is using OBUISEL_Selector reference | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files |  org.openbravo.selectors-1.0.0.obx [^] (13,523 bytes) 2014-12-02 23:16 | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0072385) alostale (manager) 2014-12-10 12:08 |
So if a field that participates in the where clause is modified and selected value in the selector doesn't match the new restrictions, it is still preserved. Similar case is reported in 19974. This would require of some UX decisions: what should happen in this case? the field with invalid value is nullified? should we have any visual hint for this? 2.50 drop downs work in this way: if the value is mandatory, new first available value in the drop down is selected; if not mandatory, it's nullified (I think). Other consideration is how this would affect performance, note these expressions must be evaluated in backend, meaning that whenever there is a change in any field involved in any of these validations, additional requests would be triggered. IMO, this issue is a design defect because all of the explained before + effort to implement it (which I think it could easily be more than 10 days). |
|
(0074503) jonalegriaesarte (reporter) 2015-02-16 11:21 |
Moved to design defect |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2014-12-02 23:16 | jecharri | New Issue | |
| 2014-12-02 23:16 | jecharri | Assigned To | => AugustoMauch |
| 2014-12-02 23:16 | jecharri | File Added: org.openbravo.selectors-1.0.0.obx | |
| 2014-12-02 23:16 | jecharri | Modules | => Core |
| 2014-12-02 23:16 | jecharri | Resolution time | => 1392418800 |
| 2014-12-02 23:16 | jecharri | Triggers an Emergency Pack | => No |
| 2014-12-03 07:32 | alostale | Resolution time | 1392418800 => 1423954800 |
| 2014-12-03 07:44 | alostale | Relationship added | related to 0019974 |
| 2014-12-10 12:08 | alostale | Note Added: 0072385 | |
| 2014-12-10 12:08 | alostale | Status | new => feedback |
| 2015-01-27 08:55 | alostale | Assigned To | AugustoMauch => jonalegriaesarte |
| 2015-02-02 13:31 | jonalegriaesarte | Assigned To | jonalegriaesarte => jecharri |
| 2015-02-16 11:21 | jonalegriaesarte | Resolution time | 1423954800 => |
| 2015-02-16 11:21 | jonalegriaesarte | Note Added: 0074503 | |
| 2015-02-16 11:21 | jonalegriaesarte | Assigned To | jecharri => alostale |
| 2015-02-16 11:21 | jonalegriaesarte | Status | feedback => new |
| 2015-02-16 11:21 | jonalegriaesarte | Type | defect => design defect |
| 2017-04-10 14:35 | alostale | Assigned To | alostale => platform |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |