Merge lp://qastaging/~akretion-team/multi-company/multi-company-action-user into lp://qastaging/multi-company

I expect that the use of this module will become clear in future modules, so I only have a couple of nits:

- better to remove the empty lines at the end of __init__.py
- l.114..119 will probably look more elegant if you break the line after the parenthesis and align with the 'o' in 'automatic'.
- l. 127 you can use orm.except_orm instead, so that you do not have to import osv at all

Thanks Stefan for the review.

Indeed, the field is used in other modules that I will propose for merging too.

I made the changes ask in your comment.

Thanks for the changes!

LGTM, The same as Stefan, I do not see the use of that field and I'm curious about the rest of modules here.

Hi, Eric Caudal has said that Elico is working on some modules for providing multi-company documents automations, so I would like to know if this module has something to do with that or is another work in progress for the same purpose. If it's so, I would recommend to talk each other to shyncronize you to avoid duplicating efforts.

Regards.

Hi,

There wasn't any answer to Pedro's question. Does this MP need review ?

Regards.

If this could help... Joël's questions help try:

When it's necesary creating an automated document from one company to another one and user working on origin company has not permission on the destiny document, any creation action produces an error so I think the field is to avoid using hardcode user_id = 1 to be passed as parameter between functions.

Just my 2 cents.

I just aprove the idea and code. Not tested code.

If you find it usefull we have got several multi-company processes created for 6.1. They have been made especifically for a customer with a very specific proccesses but maybe some code/ideas/functional aproach could be reused to build generic Odoo's full multicompany requirements. Just an idea.

I published several screencast about requirements and solution we have built (it's in spanish, sorry for that):
http://www.aula-openerp.com/soluciones-específicas-61-3/procesos-intercompañía-entre-3-empresas/
Our modules are published and available, but please contact me if you need more information about them.

Could you update the description of the module to make it clear that there is no magic done in the module.

Suggestion:

'description': """Defines a user to be used for automatic action

This module adds a field 'automatic_action_user_id'
on the company to define a specific user to be used for the automatic actions. This field can
then be used by other modules defining such actions."""

Even then, the concept of "automatic action" is not clear to me. An example would be welcome.

Hello,

The management of the project has moved to Github: https://github.com/OCA/multi-company

Please migrate your merge proposal to Github. You may want to check https://github.com/OCA/maintainers-tools/wiki/How-to-move-a-Merge-Proposal-to-GitHub for an explanation on how to proceed.

Thanks for contributing to the project