Anyone got any good ideas for the following challenge?
In our application we have a screen that lets the customer do a payment. This payment is handled by a external party in a popup. Once the user completed the payment, the 3rd party communicates that the payment is either successful or failed. This is done by a webservice. OutSystems can call this webservice and get the status of the payment back.
Now the original build process is that the screen is constantly polling this webservice every 5 seconds, and once there is a success status the next screen is loaded.
This however gives problems, as after a few minutes we run the risk of the connection between server and client (outsystems and screen in the browser) gets disconnected and/or timeout. Resulting in the screen going into error.
Now I'm aware that websockets might be a better option here, however for now this solution is rejected.
What is the next best option to handle this in the screen?
How to continuously poll the webservice to let the screen go to the next step based on the result?