Question

HTML Table from token has different borders when two different tokens are in one email.

Workflow Version 9 Business Processes

Updated May 1, 2014

asked on April 29, 2014

I created two different tokens with HTML to list field values in a table (New Accounts and Superseded Accounts). The same token (Superseded Accounts) is present in two different email activities in separate branches of a conditional decision. Although I entered the same token into the two different emails, the border appears different in the email that has two different table HTML tokens. In the email where the Superseded Accounts token is by itself, it appears like the New Accounts table below, but in the email that has both the New Accounts token and the Superseded Accounts token, the table borders are not formatted the same. I don't mind either format, but how do I get them to match? Has anybody encountered this?

Below is the HTML for the Superseded Accounts token, which is the same as the New Accounts token, except for one field (date opened/date superseded).

Create Token:

Modify Token for each iteration(append to existing values):

<tr><td class="tg-031e">%(RetrieveFieldValuesfromSearchSupersededAccounts_Client Name_1)</td><td class="tg-031e">%(RetrieveFieldValuesfromSearchSupersededAccounts_CDF - Account Number_All)</td><td class="tg-031e">%(RetrieveFieldValuesfromSearchSupersededAccounts_CDF - Date of Supersede)</td><td class="tg-031e">%(RetrieveFieldValuesfromSearchSupersededAccounts_CDF - Status)</td><td class="tg-031e">%(RetrieveFieldValuesfromSearchSupersededAccounts_CDF - Rejected Items)</td><td class="tg-031e">%(RetrieveFieldValuesfromSearchSupersededAccounts_CDF - Pending Items)</td><td class="tg-031e">%(RetrieveFieldValuesfromSearchSupersededAccounts_CDF - Maintenance Required Items)</td><td class="tg-031e">%(RetrieveFieldValuesfromSearchSupersededAccounts_CDF - CIP Exceptions)</td></tr>

Modify Token (append to existing values):

</table>

Superseded Accounts token (the same in both emails):

%(List of Outstanding Superseded Accounts#[]##"HTML"#)

0 0

Answer

SELECTED ANSWER

replied on May 1, 2014

I think it is because you are defining the style element twice (once for each table). If you define the style in its own token, or just for the first table, I think it'll work.

It worked for me when I made a test workflow with your data and deleted the style element from the second table.

0 0

Replies

replied on April 29, 2014

HTML formatting issues can sometimes be caused by Workflow adding a <br /> tag for each newline in your e-mail body.

One thing you can try doing is send the e-mail you are having problems with to a g-mail account. Once viewing the e-mail there, you can click on the little arrow next to the reply button and go to 'Show Original'. That'll show you the actual HTML that is being sent.

1 0

View 2 previous replies

replied on April 30, 2014

I was able to see the source code in Outlook, but do not see any <br/> tags anywhere in the email body. If I paste the code, would you be able to troubleshoot it?

0 0

replied on May 1, 2014

There's a good chance we will be able to troubleshoot here so lets try that first. Use the code snippet feature to paste it in.

0 0

replied on May 1, 2014 • Show version history

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">Debbie,<br><br>Below is a list of New Accounts and Superseded Accounts that have been outstanding for more than 30 days.  Per the Bank's CIP Program and New Accounts Policy, documentary customer verification must be completed within 30 days from the date opened.  If the file is designated below as a CIP Exception, and you are unable to resolve the CIP Exception, the account(s) must be closed.<br><br>New Accounts:<br><style type="text/css">.tg  {border-collapse:collapse;border-spacing:0;}.tg td{font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;}.tg th{font-family:Arial, sans-serif;font-size:14px;font-weight:normal;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;}.tg .tg-e3zv{font-weight:bold}</style><table class="tg"><tr><th class="tg-031e">Client Name</th><th class="tg-031e">Account Number</th><th class="tg-031e">Date Opened</th><th class="tg-031e">Status</th><th class="tg-031e">Rejected Items</th><th class="tg-031e">Pending Items</th><th class="tg-031e">Maintenance Required</th> <th class="tg-031e">CIP Exception (Yes/No)</th></tr><br><tr><td class="tg-031e">Linda</td><td class="tg-031e"></td><td class="tg-031e">6/2/2010</td><td class="tg-031e">Pending</td><td class="tg-031e"></td><td class="tg-031e">Test</td><td class="tg-031e"></td><td class="tg-031e">No</td></tr><br><tr><td class="tg-031e">Trinidad</td><td class="tg-031e"></td><td class="tg-031e">8/25/2009</td><td class="tg-031e">Rejected</td><td class="tg-031e">Test</td><td class="tg-031e"></td><td class="tg-031e"></td><td class="tg-031e">Yes</td></tr><br></table><br><br>Superseded Accounts:<br><style type="text/css">.tg  {border-collapse:collapse;border-spacing:0;}.tg td{font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;}.tg th{font-family:Arial, sans-serif;font-size:14px;font-weight:normal;padding:10px 5px;border-style:solid;border-width:1px;overflow:hidden;word-break:normal;}.tg .tg-e3zv{font-weight:bold}</style><table class="tg"><tr><th class="tg-031e">Client Name</th><th class="tg-031e">Account Number</th><th class="tg-031e">Date of Supersede</th><th class="tg-031e">Status</th><th class="tg-031e">Rejected Items</th><th class="tg-031e">Pending Items</th><th class="tg-031e">Maintenance Required</th> <th class="tg-031e">CIP Exception (Yes/No)</th></tr><br><tr><td class="tg-031e">Melissa</td><td class="tg-031e"></td><td class="tg-031e">4/16/2011</td><td class="tg-031e">Pending</td><td class="tg-031e"></td><td class="tg-031e">Test</td><td class="tg-031e"></td><td class="tg-031e">No</td></tr><br></table><br><br>Thank you for your attention!<br><br>*** DO NOT REPLY TO THIS EMAIL ***<br>This is an automated message, please do not reply to this e-mail.  If you have questions, please contact Operations Records Department<br><br>

Here it is. Thanks for your help!

Moderator edit: removed potentially sensitive information.

0 0

SELECTED ANSWER

replied on May 1, 2014

I think it is because you are defining the style element twice (once for each table). If you define the style in its own token, or just for the first table, I think it'll work.

It worked for me when I made a test workflow with your data and deleted the style element from the second table.

0 0

replied on May 1, 2014 • Show version history

So, I can have the style element in a separate token, and then just add that token to the body of each email? That's probably what I'll have to do, because I have a token for each table, and my workflow has a conditional decision that results in an email with one table or the other, or an email with both tables. I'm going to give that a try.

0 0

replied on April 29, 2014

Is there any way to do that in Outlook? I would have to create a g-mail account.

0 0

replied on April 29, 2014

Yes, source can be viewed for emails in Outlook. I have Outlook 2013 installed on my computer; I was able to view source by opening up the email by double clicking on it, opening up the 'MESSAGE' tab in the Ribbon interface, going to the 'Move' section, clicking 'Actions', then 'More Actions', and then 'View Source'. This command can also be added to the Quick Access Toolbar for ease of use.

This StackOverflow article suggests that the process is similar to view source in earlier versions of Outlook, but offers a few other suggestions as well.

1 0

You are not allowed to follow up in this post.

Question

Question

HTML Table from token has different borders when two different tokens are in one email.

Answer

Replies

Sign in to reply to this post.