SOAP Connector Error Handling
Hi everyone.
I have a problem with an error handling. The situation is the next:
The error appears when my app is trying to connect to a web service SOAP-type. If endpoint of WS is not available, a error is shown in the top of the Harness, but I do not want to show that. In other words, I would like to "quit" that for handling in another way.
I have tried to delete the pyErrorPage generated by that error but it does not work; the error is still appearing. I tried to setting it in a data transform of the response and creating an post load activity.
So, my question is which properties I had to set up (or delete) for avoid the appearance of that error.
Thanks in advance.
Accepted Solution
EY
ES
Gayatri, thank you for the information.
Finally, I found a solution for the error treatment. Once defined the response of the connector when endpoint is not available, I added all that req-res flow into an activity. As errors are mapped in a data transform, I just invoked Page-Clear-Message for remove the error messages.
Thank you!
CollabPartnerz
IN
Could you please find the below link
https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm
https://pdn.pega.com/community/pega-product-support/question/soap-service-exception-handling
EY
ES
Thank you for your early response.
I appreciate your information, but I have planned the solution in other way. I would like to preserve the connector and treat the error with a specific business logic, applying it in an Activity or Data Transform. For doing that, I ignore the common properties for handling error.
Any track to follow?
Thank you!
CollabPartnerz
IN
Hi,
Below link might help you.
Accepted Solution
EY
ES
Gayatri, thank you for the information.
Finally, I found a solution for the error treatment. Once defined the response of the connector when endpoint is not available, I added all that req-res flow into an activity. As errors are mapped in a data transform, I just invoked Page-Clear-Message for remove the error messages.
Thank you!