[FX.php List] Approach to update FM data from web input

[Jonathan Schwartz]

Great example, Michael.

Our email crossed each other. This looks like Option #2 that I 
described in my summary email.

I guess it depends on the volume of changes, and if staff is willing 
to review and approve.

I was also thinking that the implementation could start with Options 
2 and then perhaps migrate to the auto update options (Option 1) if 
the process proves not be in need of supervision.

Thanks!

J



At 11:12 PM -0400 8/26/08, Michael Layne wrote:
>Jonathan,
>
>We do something like this - but we "control" things a bit to insure 
>the integrity of the data in case the 
>"customer/user" inadvertently messes things up.
>
>We use a temporary table to capture what the customer CAN change, 
>then compare to what we have.  We check it, and then overwrite with 
>a click of a button for each field that doesn't match. We have some 
>tracking in place anyway, but this makes the customer happy they get 
>to control their information, and we can double-check things (for a 
>little extra control :-)).  I've included a screenshot that paints 
>the picture (Hope that is alright or is it a no-no here?)
>
>Good luck...
>
>ADDITION:
>
>oops... no attachments I guess...  here is a link to a screenshot...
>
><http://www.9degrees.com/i/data-control.gif>http://www.9degrees.com/i/data-control.gif
>
>
>Michael Layne  |  9 degrees development  |  9degrees.com  |  skype:laynebay
>
>On Aug 26, 2008, at 8:42 PM, John Funk wrote:
>
>>Jonathan,
>>I had a solution a few years ago were I duplicated the table, then put all
>>new / changed data into and kept the old data intact. Then navigating them
>>to a duplicate screen that shows the new data. This way I had an "undo"
>>function.
>>John Funk
>>
>>-----Original Message-----
>>From: fx.php_list-bounces at mail.iviking.org
>>[mailto:fx.php_list-bounces at mail.iviking.org] On Behalf Of Jonathan Schwartz
>>Sent: Tuesday, August 26, 2008 6:04 PM
>>To: fx.php_list at mail.iviking.org
>>Subject: [FX.php List] Approach to update FM data from web input
>>
>>Hi Folks,
>>
>>I'm working on a solution where the user (customer) will be able to
>>log in and update their customer information online.
>>
>>While this isn't an issue technically, there's the business issue of
>>how to process the new data without the risk of losing the original
>>data....especially if the new data is invalid.
>>
>>In my last experience in this arena, I was astonished at how
>>determined one user was to erase every bit of data presented on the
>>web form.  The customer could just clicked one box to become
>>inactive.  Instead, they felt compelled to eradicate their data.  In
>>this case, there was a second records for each customer that
>>contained the original data...the effort was futile.
>>
>>So...what do you folks do?
>>
>>Jonathan
>>
>>
>>--
>>Jonathan Schwartz
>>Exit 445 Group
>>jonathan at exit445.com
>>http://www.exit445.com
>>415-370-5011
>>_______________________________________________
>>FX.php_List mailing list
>>FX.php_List at mail.iviking.org
>>http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>>_______________________________________________
>>FX.php_List mailing list
>>FX.php_List at mail.iviking.org
>>http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>
>
>_______________________________________________
>FX.php_List mailing list
>FX.php_List at mail.iviking.org
>http://www.iviking.org/mailman/listinfo/fx.php_list


-- 
Jonathan Schwartz
Exit 445 Group
jonathan at exit445.com
http://www.exit445.com
415-370-5011
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iviking.org/pipermail/fx.php_list/attachments/20080826/063dafab/attachment.html