Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on Jul 10, 2014

RELATED IDEAS

EmailInput node should optionally output an unparsed version of the email

The email input node outputs an already parsed version of the email, e.g.
To/From/Subject appear in the EmailInputHeader, and images that are base64 encoded in the email have been decoded to BLOBs.

This allows the flow to easily parse those values, but my business requirements in some projects have required the original email to also be stored for audit purposes (e.g. in ECM). Therefore it is necessary for me to try and create a CHAR MIME structure (matching the MIME/*.eml file format) and cast to BLOB for storage.

Additionally, where the input email structure changes (switching from html/plain, containing attachments which are themselves emails) it requires complex coding or is not possible to revert the MIME tree to match the additional email.

If a BLOB which matches the original email could be included, or if there was a way to revert the EmailInputHeader & MIME to that BLOB, it would be very useful.

It is worth mentioning that my experience relates to using Microsoft Output/Exchange.

Idea priority High
RFE ID 55946
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |     Sep 11, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. We agree that this would nicely enhance the capabilities of the product. If implemented, it is likely that the new suggested behaviour of casting to BLOB would be made a non-default behaviour selected by a new configuration option on the node in order to maintain back compatability and what we suspect would remain the most common usage of the node in using a parsed representation of the email. Status of the RFE is updated to Uncommitted Candidate.

  • Guest
    Reply
    |     Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.