Suppose i use “Business Unit” security schema (for simplicity) for ORO’s Contact entities and i need to make users belongs to Business Unit “A” possible to view ORO Contact B entity.
Nowadays i need to set owner id of this contact B to one of the participants C of Business Unit A.
But the problem is that when user C would move to another Business Unit, all the A’s participants will lose ability to view contact B because of user C’s affiliation to another Business Unit. To solve this problem i should create something like ‘system’ user belongs to A, that can not be moved from A to anywhere and that should be used to link target contacts entities to A.
When contacts are created automatically (for example during some sync process or etc) the logic to determine system users (belongs to Business Unit needed) to set as owner of creating entities seems to be a little bit more ugly.
In this case ability to change ownership type “USER” to “BUSINESS UNIT” would be very appreciated. But as know it can be done now (am i wrong?).
May be there is some way to deal with relations of entities like Contacts or Accounts to Business Units in more handy way?
You must be logged in to reply to this topic.