Add page break to confirmation message

RE: Add page break to confirmation message

Mike Schmitt — Fri, 18 Feb 2022 14:45:24 GMT

Interesting workaround - it does appear to work for all intents and purposes. Since it's essentially filling the first line with enough blank spaces at the end to cause it to wrap around (no matter how short it is), it makes me curious whether it might render weirdly under different conditions / corner cases / etc. Like narrow interfaces, mobile, etc.

RE: Add page break to confirmation message

dastagirid756 — Fri, 18 Feb 2022 06:25:42 GMT

confirmMessage: padright("This is line First line.", 130) & "This is line second new line .",

RE: Add page break to confirmation message

Mike Schmitt — Tue, 08 Aug 2017 15:06:06 GMT

HTML will render as plaintext in a SAIL form. So the user would just see a confirmation message like "Line1<br>Line2".

RE: Add page break to confirmation message

siddardhas — Tue, 08 Aug 2017 14:45:34 GMT

I doubt if this will work but can you give a shot with string <br> like in HTML??

RE: Add page break to confirmation message

danak451 — Thu, 27 Jul 2017 13:31:27 GMT

Thank you, I switched it char(10) and still no luck.

RE: Add page break to confirmation message

danak451 — Thu, 27 Jul 2017 13:31:10 GMT

Thank you for the recommendation. I tried this and it works when testing the rule but not when added to the interface.

RE: Add page break to confirmation message

mukeshm298895 — Wed, 26 Jul 2017 19:56:49 GMT

Can you please try like create a simple rule inside which u store the value whatever u want and inside which you can use the char(10) functions..... After that in confirmationMessgae component simply call that rule ...It may work ...

RE: Add page break to confirmation message

Mike Schmitt — Wed, 26 Jul 2017 19:47:32 GMT

The best character to use for linebreaks in SAIL is char(10), not char(13), as char(13) is sometimes ignored.

That being said, certain component properties (instructions, confirmation messages, and various others) ignore linebreaks as far as I know - at the moment I don't believe there's any workaround to that.