|
Notes |
|
|
|
As far as I can see that problem seems to happen because your current role doesn't have access to the organisation in which the terminal is defined on, right?
So, your current organisation doesn't actually matter I think. What matters is the organisations your current role has access to. Can you confirm whether your current role has access to that particular store?
|
|
|
|
|
Antonio: "seems to happen because your current role doesn't have access to the organisation in which the terminal is defined on"
* The current role I'm trying to use has organization "Norauto France" since I am the Norauto France IT guy
* We can't expect to put in Role window > Organizaiton tab each time a store opens a new record.
* I understand that being in Norauto France organization I'm able to do actions on all the stores below (all the French stores) |
|
|
|
|
Patch proposals attached.
In any case I think this is a configuration issue. If a given role cannot manually create a new terminal from scratch in a given organization, I don't see why it should be able to do it using the copy terminal process |
|
|
|
|
|
Extra comment by Augusto: "that's how the organization access model works in Openbravo. If a role includes an organization in its Org Access tab, it gets write permissions on records referencing that organization, and automatic read access to all the organizations in its natural tree. If a role wants write permissions to records belonging to an organization, it must explicitly include that organization in its Org Access tab. " http://wiki.openbravo.com/wiki/Role [^] |
|
|
|
|
|
As discussed internally, the OB Org/Security model currently works in this way: you need to have explicit org access in your role to be able to modify records in specific organisations. |
|
Screenshot from 2020-11-02 08-46-51.png (91,677) 2020-11-02 08:55
unlinkDevice.diff (4,096) 2020-11-14 13:37