On 10 Nov 10:23, Pablo Vannini wrote: > Hi everyone > > In the TUB we made a Blueprint to manage Sales Location, in the way to > unify modules that is a common nead in the community. > The main goal of this module is to manage Sales Location (when a company > have more than one location to sale) for a Company.
I think the location should be stored on the sale. By default, it should have only set the fields that are in base sale module (so no pricelist). I don't think it is good to link the location to the user but I find it more usefull to just use the context like that it is possible to create many menu entries for each locations or use a wizard to select the location before opening the sale list. I think it is bloated to have a kind of "shop" access right management but any way, if needed this is something that could be implemented using access right on "shop" and sale. I don't understand the "default party" on the blueprint. > We should also discuss the naming conventions (shop, location, place, > etc.): > http://code.google.com/p/tryton/wiki/SalesLocation I'm in favor of location, it is quite generic and could represent a shop or a post in a shop or a set of shops in an area. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
pgpn9yORJC1IG.pgp
Description: PGP signature
