Tables in Emails...

[samwoo]

Hi,

Very frequuently we get an email from our Finance System which contains a table containing a list of records and whether or not they are errored.

A ticket is automatically generated once it detects this email. And as it should, the body of the email becomes the description of the ticket.

Howeve because it is a table, the formatting is severely messed up in the Request Details making it hard to read. Here the images should speak for themselves:

Body of the email:
#

Result in ticket:

So I was wondering if the Email Routing or Applying the Email to a ticket can detect a table and format it in some way so it's readable in the description?

Even if it's converting each row into a bullet or number

Quote

#BatchIDInErrorDateTransactionType
#BatchIDInErrorDateTransactionType

Or if it's possible to detect spaces in the text and detecting each column in a row format it like so

Quote

#Batch ID - In Error - Date - Transaction Type
#Batch ID - In Error - Date - Transaction Type
#Batch ID - In Error - Date - Transaction Type

I don't think we can amend the output of this email as I believe it's hard-coded so am hoping that there is something that can be done via the Hornbill Processing to help make these easier to read (without having to go to the Email Source each time)

(Also is Hornbill capable of having tabs?)

Thanks,

Samuel

[Oscar Stankard]

Convert table rows to CRLF and table data/column to tab character (if hornbill's text rendering engine uses tab stops) else " - " would be better than just mushing all the printable characters into a long string anyway.

[Dan Munns]

+1 for this. We receive a number of emails from 3rd parties with tables in the body as part of a report which becomes all kinds of a mess when added to the description.

[Victor]

@Oscar Stankard Hornbill uses the plain text part of an email for the request description. The plain text part (being plain text) has the printable characters already "mushed" so is not Hornbill that does it... This being said, there might be an option (possibly?) to parse the HTML table section and convert that table .... in any case, something for our product managers and devs to consider for future functionality...

[Aaron Summers]

+1

[HGrigsby]

+1 this would be useful for us too