...
Enterprise customers who build their application on the Quik! Forms Engine often want the ability to e-sign forms from directly within their own application and environment. To make this possible, the QuikESignTransport web service QuikSignixTransport sample project was developed to handle communications between Quik! and SIGNiX. In order to send a Quik! Form to SIGNiX, the data and the document must be transformed by Quik! and prepared to be sent to SIGNiX. This web service project handles the transmission of the form and data to and from Quik!, and then to SIGNiX, giving the customer full control over the steps and events prior to and after sending to SIGNiX.
In other words, a project similar to the QuikSignixTransport needs to be hosted in the customer's server, and its endpoint must be set as the SignURL of the form. If there's no interest in having this project hosted in a server, we hosted it at Quik! so that you can use it as is. The difference lies in that with this approach, the customer will not be able to do business logic after posting the data to the SignURL and BEFORE calling Signix. The URL is: https://websvcs.quikforms.com/Signix/QuikSignixTransportWS/v5301/QuikSignixTransport.aspx
Unlike the Quik! integration with DocuSign, this is the only way customers can submit a form to SIGNiX. Simply configure the relevant properties in the Quik! Forms Engine, and Quik! handles the back-end communication with SIGNiX APIs.
...