Handing of attached emails in Email Capture

[awong]

Email Capture should create a single MSG or EML source for an attached email with file attachments within a received email.  Email Capture currently creates an email body source for an attached email.  An attachment source is then created for each attachment within the attached email. 

As an example, for an email with 2 attachments; one attached email which has an attached Word file and one PDF attachment, 2 email body sources, 1 Word source and 1 PDF source will be created (total of 4) instead of 1 email body source, 1 MSG or EML source and 1 PDF source (total of 3), i.e. see diagrams below.  Under the current design, EQM users are not able to identify the relationships between the email body sources and the attachment sources and have to go back to Outlook to process such emails which means all the compliance control and reporting functions supported by EQM will be removed for those cases.

Email received by Capture

Work created by Capture

Work created by Capture with enhancement

[Karen_Hunter]

logged BPMCM-I-20 idea BPMCM-17 epic

[Karen_Hunter]

This enhancement is currently included in our plans for our next release and as we are grooming the impact, we plan to provide a configuration which will enable this functionality.  For your clients, (1) is this a global configuration or an n inbox level configuration (2) typically this means that opening the .msg natively leaves Chorus control - where this is a client decision and must be enabled for that environment - is this a correct assumption ? (3) is eqm retrieve captured email part of your solution and if so, can you confirm that you currently present that email as an attachment and there would be no expected changes?