Is it possible to send asynchronous soap calls from pega to the service bus.

Currently the soap calls are synchronous and always expect a reply message (usually a ”confirmBod” message which contains a result code (like an OK).

We prefer that our application would send an async soap call , checks the successful delivery to the service bus based on the http-status (http-200) , and does not wait for a response payload.

I tried this by changing the soap rule with property “Request only” checked. The result is that pega does not wait for a response message.
BUT it does NOT check the http-status. When I disable the endpoint on our service bus. Application did not notice that the delivery was not successful (even with a http-500 internal server error reply-status).

We also noticed there is another way to do asynchronous soap calls in Pega, but you have to setup agents and queues. I think that there is too much impact on the application.

Do anyone knows a more efficient way to do an asynchronous call which also check the http-status, please let me know.

***Edited by Moderator Marissa to update SR Details***