Question
HFix-31648 - It did not solve the problem.
We have a problem in running a rest connector that we created while still using version 7.1.8 of PEGA. When we migrated to version 7.2.2, we identified that the connector reported the following problem:
** ** A string value is required for JSON mapping. Received: [B
We follow the PEGA procedure, formalized in the link below:
https://pdn.pega.com/support-articles/string-value-required-json-mapping
We applied the HotFix - HFix-31648, however it did not show the desired effects and we continue with the same problem reported.
Could they help us?
What is the Content-Type header provided to Pega by the REST service?
It sounds like the Content-Type header has a value that does not "look like text" to Pega.
HFix-31648 should have made the logic for determining what "looks like text" more lenient. Please make sure it installed correctly.
Note: the lack of a Content-Type header means "not text," as it is ambiguous.