Inbound: Email Parser via Email2DB
Interesting concept. I've built message handling functionality using SMTP in a former life, and it worked quite well - we would send out e-mail approvals for purchasing requests from Ariba, an executive would receive the message and respond with an approval, and the inbound message would be parsed and a workflow event would be triggered based on the approver's response.
With Coghead, it would be a matter of accepting inbound SMTP, parsing the message body for inputs and triggers, encapsulating the data as XML, and routing a web service call to the appropriate account/application/collection based on information embedded in the message header or body.
Michael Topalovich, President
Delivered Innovation
mtopalovich@deliveredinnovation.com
http://www.deliveredinnovation.com
Wish:
It would be very useful to have an inbound email parser which would populate a list based on predetermined fields.
This can be used in many scenarios where as external sources (Web/Extranet/EDI) could bounce messages thus triggering inbuilt COGHEAD logic.
Usability:
Example: Tier 3 Parts Supplier in a JIT Facility receives trigger from production partner that "Part # 828181" are out. "Auto Order" to replenish supply.
Further examples of functionality, or business case support can be made available upon request
Regards,
Mark Leon