On 27/12/12 23:21 +0100, Albert Cervera i Areny wrote:
> A Dijous, 27 de desembre de 2012 21:50:07, Cédric Krier va escriure:
> > On 24/12/12 09:19 +0100, Albert Cervera i Areny wrote:
> > > In sale_opportunity module party is a required field and in the blueprint
> > > [1] nothing is said about the management of unqualified leads. In many
> > > cases, at the beginning the lead cannot have a party either because you
> > > don't know if the lead is in your target audience or because you don't
> > > even know its name (you may have an e-mail, a telephone...).
> > > 
> > > Was the management of unqualified leads alread discussed? If so, how was
> > > that designed?
> > 
> > I don't find it is a design issue. You must be able to identify the
> > party of the lead. So it will be a mistake to duplicate such information
> > that is already design on party.
> > But I agree that the name of the party should not be required as the
> > code already is.
> 
> People usually only create the party when they know that lead is actually of 
> the company's target, so in a way you try to keep the party as clean as 
> possible until you have enough information and you qualify it: that is, at 
> least you know it's name and you know of its interest.
> 
> I'd say that users will consider it possible to have duplicated leads because 
> the information may be so bad at times, but once qualified you should be able 
> to recognize it is an existing party if it is the case.
> 
> I think it is better to have a subject in the lead that lets you "recognize 
> it" such as "The cousing of customer A" and not force the creation of the 
> party with only that information. I don't think it make sense to have a party 
> with only that text in the notes.

So ok to drop the required on party but then opportunity must have a
code filled by a sequence and party must become required to be
converted.

-- 
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: [email protected]
Website: http://www.b2ck.com/

Attachment: pgpW8CyF61yJa.pgp
Description: PGP signature

Reply via email to