Capture Email: Include "RESENT FROM" Inbox in the message to use in design

[calvinfu]

As per the client's request, there is a need to enhance AWDCapture to enable Chorus to capture the entire mail header using the email capture function. Subsequently, this captured header will be passed to AWD design as an "emailstart" element.

In the workflow design, the client will be able to retrieve the mail header element and capture the sender's address using the keyword "Resend-from".

[Karen_Hunter]

Please confirm:

1. Client has multiple mailboxes used to support different processes.
2. All Mailboxes will be forwarded to a single mailbox for ingestion.
3. Capture job will process each email, prepare the message, and create a generic work item.
4. The new information available in the input message (Resent from) will be used to classify and index the items (business areas / work types / source types) in the automation service. 

Benefits include:

1. FIFO across all mailboxes
2. Simplifies model management
3. Decreases support costs 

[Karen_Hunter]

idea: BPMCM-I-2

Refactor the processing job and resulting input message.

Related request to include additional input message changes.

[jabardwell]

For our business we have multiple inboxes tied to a single Process.  Because senders can use to, cc, or bcc we find it almost impossible to understand which inbox the email was sent to.  In some cases, the "to" is a distribution list that contains the capture inbox.

We have a need to easily identify the source inbox for a capture email.  This allows us to properly apply classification rules along with routing.