CSS code was captured in email workflow


  • Hi,

    I had designed an email workflow in SharePoint Designer 2013. The workflow will trigger if the ticket falls under certain category. In the email, the description's field return value was set as plain text. The description column is a multiple line of text field with enhanced rich text. For a given ticket, the description had hyperlinks. Now, when the email was triggered, the recipient received the description value along with the CSS code (marked in yellow) in the email as shown below:

    Description             : ​I need to access the following timecards for my resource. E62A55A9042240D5A7C5715B055ACAFE .ExternalClass p.p1 { margin:0.0px 0.0px 0.0px 0.0px; font:12.0px 'Helvetica Neue'; color:#e4af0a; } E62A55A9042240D5A7C5715B055ACAFE .ExternalClass span.s1 { text-decoration:underline; } E62A55A9042240D5A7C5715B055ACAFE .ExternalClass span.s2 { color:#454545; } E62A55A9042240D5A7C5715B055ACAFE .ExternalClass span.Apple-tab-span { white-space:pre; } TS - 0235135 TS - 0239267 TS - 0239268 TS - 0239269 TS - 0239270 TS - 0243653 TS - 0243654TS - 0243655 TS - 0243656 TS - 0243657TS - 0243658​

    I am not sure how the code was captured in the email. Could you please help me resolve this issue?



    Thursday, December 29, 2016 6:09 AM

All replies

  • Hi Hiten.Patel,

    Which workflow are you using? Workflow 2010 or workflow 2013?

    Per my test in my SharePoint 2013 environment, I use workflow 2010, there is no CSS code in email when sending email by workflow. If I use workflow 2013, there is also no CCS code in email.

    To troubleshoot the issue, you could check thing below:

    1. Check if the value of the description column in list is the same as the value in the email.

    2. Set the description column as string when adding the column into the email.

    3. Create a new workflow to check if the same issue will occur.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Friday, December 30, 2016 8:20 AM