Not sure what help you require, but FWIW this is how I would approach it. First of all create your data form where the emails are stored. Try and keep the fields to a minimum to help the email submitter quickly create a ticket.
Then build a control panel that views the data form and adds the functionality you described. In terms of delete I would be inclined to implement a soft delete using a Status in case of erroneous deletions. Finally create the email template from your data form, use Email Instructions to make the template the submitter uses to be as simple as possible. i.e. The body of the email gets parsed into a single char field without the need for the !12345678! field identifiers. And don't forget indexes and archiving if the volumes warrant it. HTH Matt > > > Hello List, > > > > I need some inputs on creating an Automated E-mail application where a > Customer sends an ordinary e-mail to an inbox which will be submitted to > the ARS Inbox. I am planning to have all the e-mails from this inbox get > submitted to a holding form where I can have choice of creating a new > ticket, add to existing ticket or deleting the e-mail. > > > > I am planning on having a filter fire when a new E-mail arrives so it > gets submitted to the Email Holding form where agents can take further > actions on the email. Any input will be much appreciated. > > > > Thanks! > > > > Manjari R. Shrestha > > Junior Programmer Analyst > > > > SAIC > > 12530 Parklawn Drive, Suite 350 > > Rockville, MD 20852 > > Office: (301) 998-7364 > > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
