Errorhandling in Rest Service Connector
We are using rest connector to consume a rest service(also implented with pega) which returned different error messages in various errors.
The Service Response class has two page properties which used to map the service response:
- .Response
- .Error(if service call failed, the error page will be filled instead of response)
But in the rest connector rule we have only the option to map the service response. The error page will be full ignored.
I have considered to overwrite the OOTB ConnectionProblem, but it was in vain.
Does anyone have an idea, how could we map the error page in rest connector?
Pegasystems Inc.
GB
@LiL95470 In the case of a REST connector, you can handle different error responses by mapping the response to a Param Value. You can create a similar page structure as the response JSON for the failure status and conditionalize the mapping to PAGE (Failure status) or PAGE LIST (Success) based on the API response status CODE. You can use the Out-Of-The-Box function "pxConvertStringToPage". This approach allows you to handle different structures of responses, including error messages.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Mapping issue in ConnectRest (Exception occurred while mapping incoming res
CONNECT REST- Error Handling across the application-Design query
How to read or capture Connect-REST failure reason behind 404, 500 error cod
W&W
DE
Thanks for the reply.
But my problem is, the page structure of service response is not similar with connector response.
The service returned response page property if call successful, otherwise an error page will be retured. In this case i cannot get the error page be mapped.