Currently, when I want to send a message through the tsf_send_message stored procedure with a parameter that contains non-latin characters, such as Cyrillic and Thai, these characters are all converted to question marks.
i.e. <TEXT>"ภาษาไทย Phasa thai"</TEXT> becomes <TEXT>"??????? Phasa thai"</TEXT>.
However, as was noted in the answer to the related question, by changing the datatype of the tsf_send_message function from varchar to nvarchar, the use of non-latin characters in parameters will become possible.
Updated idea status Open → Working on it!
Hi Dries,
This idea has been implemented in the 2021.3 version of the platform and will be reviewed by my colleagues to ensure everything is made well. Not only the tsf_send_message is affected, but also the tsf_send_progress and tsf_send_assertion_msg since these procedures share the same datatype for the @parmtr_string parameter. So you can use non-Latin characters, like Thai and Chinese, in those procedures too when executing them in SQL-code
Updated idea status Working on it!→ Next release