Chorus Communications Robust Reporting

[LHumphrey]

We have been utilizing the Chorus Communications feature for some time now and have been hitting several roadblocks in terms of reporting on out bound Chorus Communications emails.  Document Delivery provides very limited details and doesn't provide us all the information we need and also doesn't allow us to go back in time over 30 days.  We are looking for values from the Work Item to be transmitted to the out bound source or recorded from the Communication Service so that we can do additional reporting required such as:

1. Create date - we can get that from the item itself when it created.
2. From Address - this can pass from the parent to the source.
3. To Address - this can pass from the parent to the source.
4. Subject Line - this can pass from parent to source.
5. Plan ID - this can pass from parent to source.
6. SSN - this can pass from parent to source
7. Result - Error/Success like in document delivery)
8. CC Address - this can pass from parent to source.
9. BCC Address - this can pass from parent to source 
10. Enclosure Name(s) 
11. Business Area - this can pass from parent to source
12. Parent Work Type - this can pass from parent to source.

Other items she brought up to pass LOB's would be:

1. Who generated the communication (Author)
2. Parent Work Item Key
3. NIGO Reason(s)
4. Doc ID
5. Comm Letter Name (Code)
6. Delivery Type (if we Print/Email/etc).

In general, would like to see more reporting capabilities around communications.

[Karen_Hunter]

Logged Idea in PM tool.  CMM-I-23

The Document Delivery defaults to the most recent 30 day date range, but you can go back to previous 30 day ranges.  Are you asking for a broader date range?

On Send Communications (finalize source) - please confirm that you are asking for the ability to configure LOB fields that can be updated on your sources?

1. Copy from current work parent includes available LOB indexing fields (similar to how you can configure the Utility cog to copy lob fields from one item to another on create) which may include LOB fields used in your packaging (but these can be changed at run time.
2. Copy from communications context includes the following "Body" data which can be changed in the packaging details experience From Address, To Address, Subject Line, CC Address, BCC Address or the "Attachment" data like Filename., 
3. Copy from communications context includes Author, Letter Name

[LHumphrey]

The Document Delivery screen does not provide the level of detail required for reporting purposes, nor does it offer export functionality or support a sufficient historical timeframe. Based on Karen's details we were are working to pass several LOB's to the sources. So then it comes to ask after that direction provided:

We request that the communications task/service in Design return, as output, all data points entered or modified within the communications user interface. Providing these values in Design would enable us to map them as LOBs on the source or transaction and build necessary reporting in Analytics.

results

cc address

bcc address

enclosure name

author 

delivery type