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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0036634
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Web POSmajoralways2017-08-10 14:012017-10-06 13:52
ReportermaiteView Statuspublic 
Assigned Tomaite 
PriorityurgentResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tomarvintm
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0036634: Permissions problem when editing business partner

DescriptionError "Entity testing (ADUser) with organization Posets Store references an entity Openbravo through its property updatedBy but this referenced entity belongs to an organization Vall Blanca Store which is not part of the natural tree of Posets Store"
Steps To Reproduce1. From POS Terminal, access to "Customers" and create "*New customer". Set name "testing" and address "testing address"
2. From backend, access User window and search the one related with "testing" business partner. Change organization to "Posets Store"
3. From backend, access User window and search username "vallblanca". Change organization to "Vall Blanca Store"
4. From POS Terminal, access to "Customers" and search "testing" customer and EDIT it to set phone number "1234". Save
5. Realize that new Business Partner record exists in Errors While Importing window: Entity testing (ADUser) with organization Posets Store references an entity Openbravo through its property updatedBy but this referenced entity belongs to an organization Vall Blanca Store which is not part of the natural tree of Posets Store
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0098788)
marvintm (manager)
2017-09-04 09:29

This issue as described cannot be fixed inside the Web POS, because it is more related to how the users and roles are configured in the backend. We need to discuss internally to decide what's the best course of action here.
(0099803)
marvintm (manager)
2017-10-06 13:52

Finally it has been decided that no change in the Retail code needs to be done to handle these problems.

- Issue History
Date Modified Username Field Change
2017-08-10 14:01 maite New Issue
2017-08-10 14:01 maite Assigned To => Retail
2017-08-10 14:01 maite Resolution time => 1504130400
2017-08-10 14:01 maite Triggers an Emergency Pack => No
2017-08-10 14:01 maite Issue Monitored: networkb
2017-08-25 10:01 jorge-garcia Assigned To Retail => jorge-garcia
2017-08-25 10:49 jorge-garcia Status new => acknowledged
2017-08-25 12:30 marvintm Assigned To jorge-garcia => marvintm
2017-09-04 09:29 marvintm Status acknowledged => scheduled
2017-09-04 09:29 marvintm Note Added: 0098788
2017-09-04 09:29 marvintm Assigned To marvintm => maite
2017-09-04 09:29 marvintm Status scheduled => feedback
2017-10-06 13:52 marvintm Review Assigned To => marvintm
2017-10-06 13:52 marvintm Note Added: 0099803
2017-10-06 13:52 marvintm Status feedback => closed
2017-10-06 13:52 marvintm Resolution open => no change required


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker