phpgroupware-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Phpgroupware-developers] addressbook model and integration with acc


From: Brian Johnson
Subject: Re: [Phpgroupware-developers] addressbook model and integration with accounts
Date: Tue, 01 Jul 2003 15:47:07 +0000

Maybe I need to explain more.

I'm hoping to link to addressbook contacts for projects in timetrack for use in 
my
company.

Those contacts are then business records that cannot be allowed to be deleted
regardless of how stupid the user is .. it can't even be an option

I would prefer that the addressbook simply post a message that app x has a 
record
linking to the one they're trying to delete

The user would then be able to go to that app and delete that record if they 
have
permissions to do so and then go back and delete the addressbook contact.

In your scenario, my app would require a method to cope with the user's request 
that
would then recreate the record they just deleted.  It means that all of these
changes to addressbook would still render it totally useless to timetrack.

I can't believe that timetrack is the only app that has this requirement.

That however brings up another point for addressbook.  I need to keep contact
information for linked contacts, even if the contact no longer exists (ie person
dies or org goes bankrupt or bought out by another company).  I can use 
categories
to designate those ones as obsolete, but it would be convenient if the 
addressbook
ui had a user pref for default filter so that only some categories would be
displayed by default in tables, etc



Dan Kuykendall (address@hidden) wrote:
>
>Brian Johnson wrote:
>> what I would like, instead of a way to allow timetrack to handle a deleted 
>> contact
>> record, is simply to prevent the deletion of that contact record (maybe with 
>> an
>> error message saying what app is linking to the contact record)
>>
>> I think this would be the easiest to implement too
>>
>> my main need is to prevent deletion, not cope with it
>
>Yes and no. We should msg the user that the record is needed by x app,
>and then if the user still insists on deleting the record, then x app
>would need to have some way to cope with it. Maybe simply deleting all
>of its associated records. The msg is all we can do, we cant really
>prevent users from being stupid, and in some cases its even possible
>that they know what they are doing.
>
>Dan
>
>
>
>_______________________________________________
>Phpgroupware-developers mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>

--
Brian Johnson
* This is where my witty signature line would be if I bothered to edit this 
line :) *






reply via email to

[Prev in Thread] Current Thread [Next in Thread]