A postback notification sends an XML file directly to your server, triggered by the completion of a form, which means your systems can intergrate the new data without having to manually input it. These notifications can save your business time and resources, which may be better spent on things other than data entry.
Setting up the Notification
You will need to have the catcher URL for your server in order to set this up which you will need to find internally. We cannot provide you with a URL for this to be set up.
When you click next, you will be asked to choose what Type of information you would like to be sent to the server.
- Simple
- Extended
- Extended with Unique Name
- JSON
- JSON with Sub-Form Data
If you wish to receive your Postback notification in XML format, there are 3 options to choose from. If your form contains a sub form, choosing Simple will provide your server with the number of rows of sub form data whereas Extended will provide the data contained within the sub form rows. Extended with Unique Name includes both the Captions and the Unique Names for all controls on the parent and sub forms.
If you decide to opt for JSON format, we offer 2 options. JSON acts in the same way as Simple and will provide all parent data and then the number of sub form rows. JSON with Sub-Form Data will include data across sub forms and nested sub forms.
There is also the option to add a Username and Password to the HTTP notification which will then password protect the data when it comes through to your server.
As with other notifications, there is the option to receive a new notification with each new Job Status if the form is attached to a Job Type. This can inform any internal workflow monitoring you may have.
Testing the Notification
Once a form has been completed, check on your internal systems for the data to have come through. This may take a few minutes, depending on your servers and what systems they are informing.