Skip to main content

Currently text parsed to the parameter is handled straight as given. 
In some cases when you would show there some text like name of a company having special characters, then the message is not coming properly.

When for example giving the input ‘<text>ROLLER Gmbh & Co. KG</text>, then the message comes incorrect showing like:



To make it correct, you have to replace the '&’ with '&amp;’ before parsing it to tsf_send_message.
Would be good if these special characters are handled within the tsf_send_message. Otherwise you have to implement a custom procedure as wrapper to do the replacement  

We cannot solve this inside the tsf_send_message task as the given string may or may not already contain the complete XML, resulting in issues if we would try to replace special characters. On our documentation page we have specified how to use the parameter string effectively and deal with special characters:

Messages | Thinkwise Documentation

While reviewing the ideas, this one caught my eye. In my opinion, this is more of a ticket than an innovative idea that we want to gather votes on (which also isn’t really taking off). Therefore, I took the liberty of reporting this as a ticket in TCP in your name and subscribing you to it. It concerns 10534S. I will close this idea accordingly.

Open→Closed
Terms & ConditionsCookie settings