2015-02-10 17:30 GMT+01:00 Cédric Krier <[email protected]>: > On 10 Feb 16:40, Àngel Àlvarez Serra wrote: >> 2015-02-10 16:11 GMT+01:00 Cédric Krier <[email protected]>: >> >> I add this two fields: >> >> cost: Float() >> >> causer: Many2One to party.party. >> > >> > What are that? >> >> Cost: cost to manage complaint.
To quantify cost. Not important could be added in custom module. > > Sorry, I don't see the usage. > >> Causer: (maybe we can find other name). Who introduce this complaint, >> culprit for example Company, Supplier, Manufacturer, Employee... > > But it is the customer who introduces a customer complaint. Used to dectect if we need to purchase to another supplier for example, because you have to many complaints that you determine that the culprit is the provider, or employee. > >> >> complaint.action >> >> complaint: Many2One to sale.complaint >> >> description: Text >> > >> > You could define an action which is simple a text. >> > >> >> type: Many2One to complaint.action.tipe >> > >> > Why would you duplicate the type here as it is already on the complaint. >> >> Because you can categorize actions. > > Why? ok, i haven't got enought arguments. removed :-) > >> > >> >> document: reference to any object of ERP, configurable (like sale, >> >> purchase or invoice). >> > >> > It is better to set an origin on the generated record. >> >> > >> >> It easy and simplier and you can manage any complaint manaually, >> > >> > It is already the case with the proposal. >> > >> >> whith >> >> this designs you can manage refund, or give a present and let for >> >> other modules to make automation. >> > >> > Idem with current proposal. >> >> But, I try to manage any type of complaint not only sale to make >> extensible. > > I don't understand which other complaint you try to manage. > I already stated that supplier complaint will have a different workflow > (just like purchase has a different workflow from sale). > I will try to explain despite my English. I don't think that purchase, shipment or invoce complaint have different workflow if you remove sales. specific funcionality and fields >> > So you just want to have no action per default an having an other module >> > for each major modules like sale, account_invoice etc. >> > I don't think it diserve that as for me, customer complaint needs a >> > customer and such parties are in a large cases created by the sale >> > module. >> >> Yes, but you can receive a complaint for a delivery, invoice. > > Yes it is supported by the current design. yes, but actions it's only related sales refund and credit notes. > >> We have a requirements thar customer complaint about one Lot, again it's >> related to sale, but solution not always it's a refund or credit note. > > Feel free to implement new actions. As usual with the Tryton design we > don't cover all cases but we design the solution to allow to cover all > cases. > >> > Of course, you can imaging company that do only project basis business >> > and so they don't have sale module installed but first it will be >> > strange for such company to manage customer complaint instead of a >> > project task; secondo they still could instal sale module without using >> > it. >> > >> >> I think we can reuse complaint model if we split modules for complain and >> for sales relation action/fields. > > I still don't understand. > > -- > Cédric Krier - B2CK SPRL > Email/Jabber: [email protected] > Tel: +32 472 54 46 59 > Website: http://www.b2ck.com/ -- Àngel Àlvarez Serra Tel. 93 553 18 03 @aasnan www.NaN-tic.com Avís legal >> _______________________________________________ Nan mailing list [email protected] http://lists.nan-tic.com/listinfo/nan
