Here is the newest feature: save your sent requests. This feature allows you to store any sent request. After you stored it in our database, you are able to use it later in order to automatically fill in the web interface fields. To do so, you first need to load the method definition. Then you fill in the fields and send the request. Finally, if no system error occurred, you are able to save it securely.
We also gathered all actions related to the current loaded method into one button.
First step: load the method
To send a request, your first need to load the method web interface. When the web form is loaded, you can fill in the fields required to send the request. In this sample, we also set fake HTTP Headers. Indeed, we aim to ensure that HTTP Headers are well stored and loaded later. Here is what we use as values to send the request:
Second step: send the request
After filling in the fields, send the request pressing the Send request button:
Even if an error occurred because we set wrong parameters values, this error is not a system error. Thus we can store the request.
Third step: save your request
As we said, we gathered actions related to the method into one button:
These actions are available on top of the page. As you can see, the reload method definition has been moved to this new menu. The second entry will be used lastly. What we use now is the Save the request entry. Clicking on it opens this overlay interface:
By default the Title and Description fields are filled in with respectively the current time and the current called method. You can personnalize these two fields so you'll identify them easily for your needs. After the changes, don't forget to click the Save changes button. If you made an error, don't panic. You can still load again this interface that will load your saved values. As soon as you don't send a new request nor load a saved request nor left the page, you can edit it as many times as you want. Once you saved it and left the page or load a saved request or sent a request, you can't edit it. But you can delete it.
Fourth step: visualize and load saved requests
After you saved request, you can visualize them by clicking the Load a request menu entry. This entry will display this overlay interface:
As you can see, we have our last saved request saved with the ID 803. And we also have previous saved requests with personnalized values as for the Title and the Description.
What you can also see is that we clicked on the play 
icon of the saved request with ID 803. As soon as you click on it, it displays the loading 
icon to indicate that it's loading the saved data from the server then automatically fill in the web interface form fields. As you can imagine, the more the saved request is complex and have deep parameters, the longer time it will take to fully fill in the fields. But don't panic, it's only a matter of seconds! When the saved data of the request have been downloaded from the server and the first level parameters have been filled in, the overlay interface fades out and the process continues to fill in the fields until the last one. Just wait a few seconds and you should have all the saved data loaded in the web interface form fields. Then you can right away send the loaded request as if you filled in the fields yourself.
Saved request data are stored forever until you decide to delete them using the trash 
icon. Before actually deleting the saved request, you are asked to confirm the deletion. Deleting a saved request only takes a few seconds. You won't be able to use it anymore and it will disapear from the list of the saved request interface.
Conclusion
We think it's a really useful feature for users who actually send request often with similar parameters. It's also useful when you send same requests very frequently to get actualized data from a distant service.
You must also know that this will the core feature of the next new feature that will follow. The next feature will allow anyone with an account to get the response of a saved request using a REST Web service. It will be a real SOAP to REST Web service because you'll be able to override saved parameters in order to customize the SOAP request before it's actually sent to the SOAP Web service. And all will done through the REST Web service we'll provide.
If you're interested in this next feature and want to know more about it or if you have any suggestion about the existing ones, feel free to contact us or post a comment.