Capture - eMail Capture to create email content source with inline images

[awong]

eMail Capture should support the option of creating an email content source with inline images included in the same source rather than separate sources attached to the same work such that the email body with the inline images will be stored and displayed as a single source in Content Viewer. 

Inline images are currently created as separate sources attached the same work. It is very hard for users to relate the email content to the inline images when there are multiple images and any incorrect reference may result in errors with financial risks.

In the example below, one single source (as shown below) should be created instead of 2 sources (1 email body and 1 attachment source for "ABCCo Funds").

 

[Karen_Hunter]

The Email capture job, regardless of protocol, should prepare one and only one body to submit with the email message input.

Current line of thinking should process as follows (best body concept):

·       If HTML then one HTML body plus attachments

·       If Plain Text then Plain Text body (plus attachments - if any exist) 

Older versions of the processing job create two bodies for rich text/html emails - resulting in the desired rich text body with all in-line images intact, along with a plain text version which created any in-line images as attachments.  Unless there is a compelling use case provided by a client, the job will produce one and only one body with no unnecessary in-line images as its default.

idea: BPMCM-I-7

epic: BPMCM-17