Paragraph Field Data into Body of Email

RE: Paragraph Field Data into Body of Email

harshav — Thu, 21 Jun 2018 11:09:16 GMT

Great thanks Mike,

Let me have a look

RE: Paragraph Field Data into Body of Email

Mike Schmitt — Wed, 20 Jun 2018 14:56:45 GMT

but the business wants that as & not &.

So i'm still having trouble trying to figure out what you mean by "& not &". Can you maybe insert a screenshot of what exactly looks wrong in the generated document?

Also just for reference - if you open the XML contents of a word document and find the text where the "&" character is stored, you will see that in the background in Word it's stored as literally the exact same thing,

"&amp;amp;".

So I don't know how much more we can do from Appian since we're passing in the exact same characters used by Word itself.

RE: Paragraph Field Data into Body of Email

harshav — Wed, 20 Jun 2018 14:51:12 GMT

In the Example given above,

when i pass all the special characters it is accepting all of them, but the character & is converting into & amp and printing in doc and if you see < is converting to & lt into the doc.

but the business wants that as & not & amp. so is there a way we can get this.

I am actually using this convertion and using that data into a word document from template.

and i know without this conversion the symbols & < > are not acceptable.

RE: Paragraph Field Data into Body of Email

Mike Schmitt — Wed, 20 Jun 2018 14:47:58 GMT

Can you clarify what you mean by "&" itself ?

RE: Paragraph Field Data into Body of Email

harshav — Wed, 20 Jun 2018 14:44:53 GMT

Sure Mike,

My problem is....

is used this code

=tohtml(
reduce(
fn!substitute,
trim(pv!remarks),
merge(
{ "&", ">", "<", char(10), char(13) },
{ tohtml("&"), tohtml(">"), tohtml("<"), "</w:t><w:br/><w:t>", "" } )))

and could able to get the word document working and could generate that....

Now wherever the data contains & it is replaced with &amp which is what tohtml is doing.... but as per the requirement they need "& "as is in the word doc.

So any suggestions to get it like "&" itself in word.

RE: Paragraph Field Data into Body of Email

Mike Schmitt — Wed, 20 Jun 2018 14:40:04 GMT

Could you rephrase that? I'm having a hard time figuring out what exactly you're asking.

RE: Paragraph Field Data into Body of Email

harshav — Wed, 20 Jun 2018 14:05:44 GMT

Hi Mike,

Just on the other note, we are now using to put this into a word document which i am sucessful with the code in which you have givne in previous comments, but when i am trying to pass Special characters like & < and > i could able to convert them to &amp &lt &gt but is there a way in my document can i get it like & < > symbols any help please

RE: Paragraph Field Data into Body of Email

Mike Schmitt — Tue, 05 Jun 2018 12:20:40 GMT

If you populate the multiple line breaks in Word (instead of generated in Appian) as a test, and then feed that through PDF from Docx, does it work as expected then?

RE: Paragraph Field Data into Body of Email

harshav — Tue, 05 Jun 2018 11:44:48 GMT

My Question for the email body is solved and I need to have the same body of that which is saved in a Process variables popped up on a pdf page... it is coming perfectly in word after what mike suggested. But I am looking some options for PDF in PDF the line breaks are considered only 1 not the way it is coming in word.

so facing issues.

Any help in this.

RE: Paragraph Field Data into Body of Email

Shanmukha — Tue, 05 Jun 2018 05:33:49 GMT

Hi Harsh,

Since the email is all about including the html stuff so you can use </br/> tags.

Thanks

RE: Paragraph Field Data into Body of Email

harshav — Mon, 04 Jun 2018 18:36:56 GMT

Thank you Mike, is there any better option to directly create a PDF document with the body ....
If so please suggest

RE: Paragraph Field Data into Body of Email

Mike Schmitt — Mon, 04 Jun 2018 16:15:43 GMT

I'm not very familiar with the PDF from docx plug-in; as far as I know it might intentionally strip out extra linebreaks during conversion for space saving or for other technical reasons.

RE: Paragraph Field Data into Body of Email

harshav — Mon, 04 Jun 2018 15:52:17 GMT

The Only problem in PDF is it is giving only one line break

post that how many line breaks it has it is ignoring.....

Any help on this pls.

RE: Paragraph Field Data into Body of Email

harshav — Mon, 04 Jun 2018 15:35:41 GMT

Thanks Mike,

This problem is solved and this i could able to achieve this...
but when i am trying to convert to PDF , it is not coming properly, Fr this is there any changes to be done.... sorry for bugging you.

I am using PDF from docx

RE: Paragraph Field Data into Body of Email

Mike Schmitt — Mon, 04 Jun 2018 15:08:51 GMT

Namely, you'd need to use a special specific line break code that Word knows how to read. The other characters can remain the same. Here's my "word text sanitizer" rule:

reduce(
  fn!substitute,
  trim(ri!input),
  
  merge(
    {
      "&",
      ">",
      "<",
      char(10),
      char(13)
    },
    {
      tohtml("&"),
      tohtml(">"),
      tohtml("<"),
      "</w:t><w:br/><w:t>",
      ""
    }
  )
)

RE: Paragraph Field Data into Body of Email

Mike Schmitt — Mon, 04 Jun 2018 15:05:29 GMT

For word documents, it requires similar coding but the replacements are different, as you need to use WordML instead of HTML.

RE: Paragraph Field Data into Body of Email

harshav — Mon, 04 Jun 2018 15:01:31 GMT

I have a quick question mike, on this,

What if i wanted to put the same in the word document and display it as document then what should be done,

When i tried the same doing it calling in the word document from template it is throwing this error.

We are sorry we cannot open the document as it is having the error in its content.

Can you please suggest on this if you have any idea on this.

RE: Paragraph Field Data into Body of Email

harshav — Mon, 21 May 2018 16:07:10 GMT

Thank you so much Mike it is working perfectly fine.

RE: Paragraph Field Data into Body of Email

Mike Schmitt — Thu, 17 May 2018 17:26:27 GMT

You probably want to make an expression rule which you can pass any text through when using in an email, as email text has its own special quirks as well as HTML formatting.

I've used the following expression rule for a long time now and it's worked well. It replaces regular line breaks (char(10)) with "<br/>" tags, replaces secondary line breaks (char(13)) with null, and replaces "&", "<" and ">" with their HTML equivalents, to reduce the risk that they cause issues when entered by a user.

reduce(
  fn!substitute,
  trim(ri!input),
  
  merge(
    {
      "&",
      ">",
      "<",
      char(10),
      char(13)
    },
    {
      tohtml("&"),
      tohtml(">"),
      tohtml("<"),
      <br/>,
      ""
    }
  )
)

RE: Paragraph Field Data into Body of Email

harshav — Thu, 17 May 2018 11:56:45 GMT

Yeah this is working fine for me and thank you for this.

RE: Paragraph Field Data into Body of Email

Vinay Kumar Rai — Thu, 17 May 2018 11:52:06 GMT

The best option is to substitute the char(10) to <br> while sending to Email body

local!myText:
"ABC
asdas
sdfsdfds
",

local!EmailBody: substitute(text:local!myText, find:char(10), replace_with:"<br>")

RE: Paragraph Field Data into Body of Email

harshav — Thu, 17 May 2018 11:49:13 GMT

it is with Using the Email template as adhitya suggested.

RE: Paragraph Field Data into Body of Email

harshav — Thu, 17 May 2018 11:48:47 GMT

these are the screenshots which is the process.....

RE: Paragraph Field Data into Body of Email

ravalik — Thu, 17 May 2018 11:43:09 GMT

If possible share your screen shots to get better understanding on your issue

RE: Paragraph Field Data into Body of Email

harshav — Thu, 17 May 2018 11:42:00 GMT

We cannot predict what the user might enter in the paragraph right then I don't think I cannot put line breaks on that....