Encoding issue with Appian 20.1

RE: Encoding issue with Appian 20.1

Julien Fontaine — Wed, 27 May 2020 16:14:58 GMT

I don't think there is a way (or I have not find it) to define the charset of the response in an integration component.

I am submitting a product enhancement request to add afield on the integration component configuration view that allows the user to set the default charset setting.

RE: Encoding issue with Appian 20.1

Claire — Wed, 27 May 2020 16:05:20 GMT

Thank you for your response.
If I understand correctly, this will work while defining a Web API component, where the header can be forced in the httpResponse function.
But If I'm using an Integration component, is there a way to define the charset of the response ? I can define it as a request header, but I'm still having issues with the response.

RE: Encoding issue with Appian 20.1

Julien Fontaine — Wed, 27 May 2020 15:35:54 GMT

Hello Claire,

If I understood well the support, with 20.1 version, they added the following behaviour to the integration components :

- if there is no charset defined in the Http Response, Appian set the encoding with the default value ISO_8859_1

- if the charset is defined, Appian uses the charset from the response

Actually, it seems that the only way is to configure your API to send the charset in the respons : Content-Type: application/json;charset=UTF-8

It worked for me.

RE: Encoding issue with Appian 20.1

Claire — Wed, 27 May 2020 15:17:47 GMT

Hello Julien,
I have exactly the same problem. Did you have any answer from the Appian support ?

RE: Encoding issue with Appian 20.1

Julien Fontaine — Tue, 05 May 2020 13:56:14 GMT

Thank you Mike for your answer.

I will open a support case.

RE: Encoding issue with Appian 20.1

Mike Schmitt — Tue, 05 May 2020 13:37:46 GMT

It sounds like nothing changed on your side or within your integration, so I recommend that you skip straight to opening a support case with Appian on this.