Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0007689
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] C. Securitymajoralways2009-02-19 18:422009-05-22 19:36
ReporterpsarobeView Statuspublic 
Assigned Toiciordia 
PriorityurgentResolutionopenFixed in Version
StatusscheduledFix in branchpiFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0007689: 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
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0016196)
iciordia (manager)
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

- Issue History
Date Modified Username Field Change
2009-02-19 18:42 psarobe New Issue
2009-02-19 18:42 psarobe Assigned To => eduardo_Argal
2009-02-19 18:42 psarobe Regression testing => No
2009-05-07 10:07 psarobe Status new => scheduled
2009-05-07 10:07 psarobe Assigned To eduardo_Argal => pjuvara
2009-05-07 10:07 psarobe fix_in_branch => pi
2009-05-09 12:24 iciordia Note Added: 0016196
2009-05-22 19:36 pjuvara Assigned To pjuvara => iciordia


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker