Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007689Openbravo ERPC. Securitypublic2009-02-19 18:422009-05-22 19:36
Reporterpsarobe 
Assigned Toiciordia 
PriorityurgentSeveritymajorReproducibilityalways
StatusscheduledResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0007689: Security reference data in master data windows is not correctly handle
DescriptionImagine this organization tree:
*
--Spain
       --Pamplona
       --Barcelona
--USA

And you have Product categories for all the organizations, so 5 categories

Right now if you create a product in Spain, you are able to see in the combo product category the following categories created for * (this is correct), Spain (this is correct), Pamplona (this is wrong) and Barcelona (this is wrong)

Why is it wrong? because if Spain has accounting but not Pamplona and I create a product in Spain but selecting a category in Pamplona, this product will not have accounting as the accounting for a product inherit the accounting defined for the category itself.

You should only see the categories created in his own organizations and all its ascendants
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-02-19 18:42psarobeNew Issue
2009-02-19 18:42psarobeAssigned To => eduardo_Argal
2009-02-19 18:42psarobeRegression testing => No
2009-05-07 10:07psarobeStatusnew => scheduled
2009-05-07 10:07psarobeAssigned Toeduardo_Argal => pjuvara
2009-05-07 10:07psarobefix_in_branch => pi
2009-05-09 12:24iciordiaNote Added: 0016196
2009-05-22 19:36pjuvaraAssigned Topjuvara => iciordia

Notes
(0016196)
iciordia   
2009-05-09 12:24   
This is a known issue of current security model that we decided to manage in future enhancements. Right now the rule is that you can assign references within the natural tree of the referencing record organization, which is the only rule flexible enough to be applied to all Openbravo tables. The solutions would be to be able to define for each table if it can be refered from the natural tree, only from ancestors (eg. product categories), only from descendants or only from the original organization