Here is what you need.. Forms:
1. Incoming Processor: This form will store all Incoming Messages and process the message for an Update/ Create action. 2. Rules: This form will be used to configure rules to create Requests based on the Incoming message either based on the incoming email address or a keyword in the subject line. Example: · If the message is from sender X, create an Incident and assign to Support Group 1. · If the message has a "KEYWORD" in the subject line, create a Work Order and assign to Support Group 2. Workflow: 1) Create a Filter on “AR System Email Messages” that will execute on Submit and push all Incoming Messages to “Incoming Processor” form. 2) Filters on “Incoming Processor” a. Check the subject line if it contains Incident/ Problem/ Change/ Request/ Work Order/ Task number. If “Yes”, parse the number and create the corresponding work log entry. b. If the message doesn’t fall into “Update” action, check if there are any associated rules in “Rules” form for a Create action. c. If none of the above, ignore the message. Thanks Mahesh On Mon, Apr 16, 2012 at 6:31 AM, Jose Huerta <[email protected]>wrote: > ** Yes, that was my idea. But not a display only form, but a regular one. > To store a log of performed actions. Anyway, seems that I'm in the right > direction. > > Thanks, > > Jose > > > > > On Mon, Apr 16, 2012 at 13:26, Jlbess <[email protected]> wrote: > >> ** >> Jose, >> I typically create a display only form to handle inbound email. Keeping >> minimal customization on the OOB forms. Just a push field filter from AR >> System Email Messages. You can then use the custom form to pull data, >> parse, configure, and push anything where you need it to go without any OOB >> customization. >> >> Jason >> >> >> >> On Apr 16, 2012, at 7:07 AM, Jose Huerta <[email protected]> >> wrote: >> >> ** >> Hi all, >> >> I want to receive email from users, perform complex evaluations on it, >> and act accordingly. >> >> For instance, If a pattern like INC____________ is found, then look for >> the incident, add the content of the email as a work info, where the sender >> must be the user corresponding to the sender address, and generate a >> response email. If not, send an error mail. >> >> Well, My idea is to config an email inbox without parsing and create >> filters on AR System Email Messages form. Don't know if it's the better >> approach. Comments or suggestions? >> >> Parsing engine at the email engine seems to be insufficient, because >> users can use a lot of formats. >> >> Thanks, >> >> Jose Huerta >> http://theremedyforit.com/ >> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ >> >> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
