Posted: 1 Aug 2017 9:32 EDT Last activity: 16 Oct 2018 12:03 EDT
In a CONNECT-REST the response status text is not received
When I'm doing a POST request to a REST service by using a pega REST connector, it always returns a responsecode, like 200, 400, 500 etc, which is mapped to pyHTTPResponseCode.
Alongside the responsecode a REST service also returns a status text like "Bad Request", "OK", "Internal Error", "Not Found".
The external, proprietary, service we call does not send standard status texts, but sends custom status texts. For instance on status 400 it sends "Missing 'To' or 'Recipients' property" in stead of "Bad Request".
I would like to get that custom text, so i can show it to the user.
Is there a possibility to get this from pega somehow. I could not find it on any page (local page, param page, step page), see attachment.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
I just had a look, but this property has the value:
the HTTP response code of 400 indicated a client error. The response data may contain a reason. // The body of the service's response, which is set up for mapping in the Connector rule, was empty for this service call.
I looked at the activity ran by pega (Invoke and pyInvokeRestConnector) and this is a value set by pega when the result is not 200. But it is not the status text.
I already checked it there, but couldn't find it. The person handling the SR (Sergei Moisseyev) told me it would be fixed either in 7.3.1 or 7.4 with the enhancement mentioned earlier. But there is no way for me to check the enhancement myself witg pega, so he told me to ask for it on the community.
Is there someone who can confirm if ticket FDBK-22765 is fixed in 7.3.1 or will be fixed in 7.4?
On our internal portal FDBK-22765 shows that it is not resolved. The best way forward is to talk to your Account Executive who will be able to get this information for you. Release timelines or features of a future release might be considered internal and not shared on our community.