--- On Sat, 3/13/10, Vani Hebballi <[email protected]> wrote:
>
> First case:
> Create a user and login to the end user portal of this user
> and create
> the following contacts with the below mentioned fields :
>
> 1.First name : Aadya ; Last name : Sen ; Phone : 123
> 2.First name : Aadya ; Last name : Sen ; Phone : 123
>
> I have added two contacts with same first name, last name
> and phone
> number which are mandatory fields but the user is NOT
> ALERTED with any
> message that the contact already exists. When there are
> large number of
> contacts in the phonebook , if the user is not alerted ,
> unnecessary
> duplicate entries will be present in the phonebook.
>
> Shall I raise a bug for this?
>
> Second case : Create a contact with following details :
>
> 1.First name : Saanvi ; Last name : Sen ; Phone : 456
> 2.First name : Ananya ; Last name : Sen ; Phone : 456
> While creating the SECOND contact in the second case, user
> should be
> alerted with a ALERT MESSAGE something like "Phone number
> is already in
> use for Saanvi, do you want to continue?" If the user says
> yes, the same
> phone number should be saved with two different names
> otherwise this
> should not be allowed.
>
> Third case : Create a contact with following details :
> 1.First name : Amogh ; Last name : Sen ; Phone : 789
> 2.First name : Amogh ; Last name : Sen ; Phone : 666
> While creating the SECOND contact in the third case, user
> should be
> alerted with a ALERT MESSAGE something like "Contact name
> already
> exists, do you want to replace? If user says yes , then
> number has to be
> replaced otherwise user should not be let to create two
> contacts with
> same name.
>
> Is this expected behavior or should I raise improvements
> for second case
> and third case?
I just tried to create 2 accounts in gmail with the same name and is working
just fine.
I also tried the mentioned scenarios on the iPhone phonebook (though not sure
if it's the best phonebook behavior to compare with) - it doesn't enforce any
of the above.
IMO we should not enable this constraints (will also introduce overhead on
creating new entry / importing from csv or gmail - phonebook entries will have
to be searched and compared for each)
George
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
