openerp-connector-community team mailing list archive

[Guewen Baconnier <guewen.baconnier@xxxxxxxxxxxxxx>]

Hi Eric,

I rapidly read through your specs, that's a terrible beast that you are 
willing to overcome ;-)

But it's also something that would interest many people I guess.

My impression is that the connector is a good foundation to build such 
an intercompany connector. It could ease the development with the jobs, 
the events, the possibility to change the behavior according to the type 
and version of the backend (with a hierarchy), ...

However, I fear that it won't help much for the problems you actually 
incur like the ACL issues. Another potential issue you should be very 
vigilant with is the synchronization loop, but I think you already took 
care of that in your current solution.

If I had to develop something like that today, I would use the connector 
framework.

Best,

--
Guewen Baconnier
Business Solutions Software Developer

Camptocamp SA
PSE A, CH-1015 Lausanne
Phone: +41 21 619 10 39
Office: +41 21 619 10 10
http://www.camptocamp.com/

On 09/07/2013 06:21 AM, Eric Caudal wrote:
> Hi,
> We have been working on Multi-company capabilities and we are getting to
> some workable module. Nevertheless we are not very happy with the result
> (not generic enough and still with some ACL issues).
> With the combined experience of the Magento connector and the
> multi-company features I came to a new approach that I would like to
> briefly submit here for feedback, in search for guidance and community
> approach.
>
> The business case and general requirements for ICOPS are available in
> the following blueprint:
> https://blueprints.launchpad.net/multi-company/+spec/icops
>
> I am considering using the current Magento connector framework (with
> setup, queues and job functionalities) to manage the communication
> between companies based on the following concept:
> - a connector would be setup (with the user rights etc.) for the
> destination company to accept request (like current API from Magento).
> Every company allowed to accept intercompany request should have the
> proper "connector" setup to accept request (eg: a company A can only
> accept request from company B not C and only for PO creation).
> - a setup for the origin company to trigger ICOPS action based on event
> for the given object (eg:  for the SO, on creation, create a PO in
> destination company with possible additional options).
> - Event: object creation, confirmation, deletion and update.
> - Objects: PO, SO, CI, SI, IS and DO.
>
> Whenever the event is triggered a job would be queued and processed by
> the cron application (as in current Magento connector).
>
> Would this approach be generic enough to fulfill most of the case and
> avoid ACL problems on creation etc.?
> NB: This approach could be extended for EDI purposes between companies
> (mainly taking advantage here of the queued communication framework and
> mapping facilities).
>
> Your thoughts?
> --
> Eric CAUDAL
>
> Eric Caudal
> /CEO/
> --
> *Elico Corporation, Shanghai branch
> /OpenERP Premium Certified Training Partner/  *
> Cell: + 86 186 2136 1670
> Office: + 86 21 6211 8017/27/37
> Skype: elico.corp
> eric.caudal@xxxxxxxxxxxxxx  <mailto:eric.caudal@xxxxxxxxxxxxxx>
> http://www.elico-corp.com
>
> Elico Corp