Contributors mailing list archives
Re: Proposal to add Operating Units to OCAby
Camptocamp SA, Joël Grand Guillaume
Not sure if it is better a dedicated repo or split it in every area, any ideas, pros and cons ? On my side, somone wanting to use OU will probably use them evrerywhere or nowhere. So having a dedicated repo seems fine to me.
Hi Jordi,Thanks for this contribution. Of course I'm 100% committed to add it into the OCA.
On Wed, Dec 2, 2015 at 12:53 AM, Naran M <email@example.com> wrote:
Thank's Jordi. It's brilliant. Looking forward a use case demo.On Wed, Dec 2, 2015 at 4:23 AM, Jordi Ballester Alomar <firstname.lastname@example.org> wrote:Thanks Pedro,We'll define a group "Usability / Multi Operating Units" and hide the field unless the user belongs to this group.As for the required field, we could well have it as a non-required field. That would be a good idea.The important thing that we will validate is that there's consistency across the linked models. For example, you will not be allowed to create a Purchase Order with no operating unit, and then have the associated Invoice be assigned to an Operating Unit. It would be either no Operating Unit at all, or the same assigned across the linked models.Regards,Jordi.Creating one operational unit, making it default for all, and hiding the field if the group is not selected can be enough. Anyway, I always prefer not to have extra required fields. Can be logic adapted to not require it?Regards.What I also realize is that the the operating unit is a required field in every model where it is introduced (e.g. purchase order). That would make all the repositories depend on the operating unit model when they are run on runbot. Quite a hard dependency to add to all repos.On the other side, the operating units could just be transparent in the process if you don't specify a flag 'Multi-Operating Unit', as it is now the company model for a user who is allowed to access to a single company and has the 'Multi-Company' flag unchecked. But would be running behind the scenes.Frederic, the problem I see is that it virtually impacts all areas, so this repository would have lots of dependencies with other ones.If the concepts are adopted by the community, in time it makes sense that each repository should have it's module on operating units.But I'm open to any proposal by OCA members.Fantastic work Jordi.I am wondering if it does not deserve a specific branch
+1Jordi,To me that sounds like a cool work that allows to look at the company from different angle. I have ran through specification and looks like it can be applicable for many companies. I know even personally organisations that starting to implement "Business Units" working within one legal entity.That is quite typical for large companies.And if you can schedule a demo - definitely I will be happy to participate in it.///
Technical Director, XPANSA Group | ERP, BI, E-commerce, Data Mining and DMS consultingDear OCA community,We'd like to propose our work done on Operating Units to be added to OCA.The work is documented here:https://docs.google.com/document/d/1iF2tKqCGjpZhTABU4oBT62sM08JFuNBXOtChbOSyBXQ/editThe current repository is here:If there's interest I can schedule a session or two to go through the features functionally.The working version has been 7 so far, but we're starting to port to v8 now.What we'd need to know is how to move the work to OCA.You can find our starting proposal here:https://docs.google.com/spreadsheets/d/1sacGPz9ofbD0s8Q-jgioFUvvabJD_weqknNzsd2J7X4/edit?usp=sharingYour feedback is much appreciated!