#1 - Ability to customize email body dynamically from data flow. Currently if we select "xport-smtp-datalocation" as "ATTACHMENT" in routing rules, it assigns body of the email as generic value "Smtp from: Business Alias". We would like to have the ability to populate body of the email based on trading partner/transaction from map updates to process data. Currently we do this for subject line of the email (by updating DestinationProtocolSubject)...Similarly we would like to have the ability to update info in process data for text that needs to be passed in body of the email (something like by updating DestinationProtocolEmailBody etc) and have SMTP business process use that information for building body of the email.
#2 - Ability to send same payload in BODY of the email as well as ATTACHMENT. Currently "xport-smtp-datalocation" assignment supports only "BODY" or "ATTACHMENT", but not both. It would be nice to have the ability to send same payload in body as well as attachment (some customers requested this as they want to see content in body of the email for quick verification and use attachment to save it for archive purposes)
#3 - Ability to send original input file and post translated output files as EMAIL attachments (more than one attachment to the email). We have seen few customers requesting this especially for their rip&read human readable flows...These are documents that they don't integrate with their backend ERP system and instead we map them into human readable report format and email it to their customer service teams. When emailing to customer service, they would like to see what came in from partner (original EDI) and post translated human readable format both attached to their emails (for cross verifying in case they need it). Previous two requests take priority when compared to this last one.