Question
Bradesco Seguros
BR
Last activity: 16 Jan 2018 9:27 EST
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:
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?
Accepted Solution
Pegasystems Inc.
US
To be clear, I was not trying to suggest a configuration change in Pega.
You need to find out what value the remote server is putting into the Content-Type header, in order to diagnose Pega's behavior.
Unfortunately, you cannot get this information from Pega's logs. If you have access to the service side, the Content-Type may be logged there.
There are many ways to check this. Perhaps you could use PostMan or some other free tool to make the HTTP request and inspect the response headers.
Alternatively, you could contact the service provider and ask them what the Content-Type header is set to for the API you are calling.
There's a chance you could influence the service's behavior by configuring your Connector to set the "Accept" request header to "application/json" so that the service knows what content type you are expecting.
Pegasystems Inc.
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.
Accepted Solution
Pegasystems Inc.
US
To be clear, I was not trying to suggest a configuration change in Pega.
You need to find out what value the remote server is putting into the Content-Type header, in order to diagnose Pega's behavior.
Unfortunately, you cannot get this information from Pega's logs. If you have access to the service side, the Content-Type may be logged there.
There are many ways to check this. Perhaps you could use PostMan or some other free tool to make the HTTP request and inspect the response headers.
Alternatively, you could contact the service provider and ask them what the Content-Type header is set to for the API you are calling.
There's a chance you could influence the service's behavior by configuring your Connector to set the "Accept" request header to "application/json" so that the service knows what content type you are expecting.