iFormBuilder Data
What's covered:
Also, be sure to check out:
What is Post Data?
Post Data is similar to the e-mail report in that it pushes a copy of the record data out of iFormBuilder to a user-defined web page (while maintaining the original record on the iFormBuilder database). This action takes place every time a new record is successfully uploaded to the server, or an existing record is updated.
How do I create a Post Data endpoint?
To create a Post Data endpoint, please follow the instructions below.
STEP 1. Form the admin portal, hover over the Forms tab and select Form Assignment.
STEP 2. Highlight the form you'll be working with and click Assign.
STEP 3. Scroll down to the Post Data section and click + New Endpoint.
STEP 4. Enter the details of your endpoint.
- Name: The name of the POST service.
- Endpoint URL: The address iFormBuilder will send data to when a record is called for POST process
- Post Data Format: The data format you want to be delivered to the endpoint (XML, JSON).
- Post Body Content Type: Encoding format of the data being sent to the endpoint. Options will vary depending on Post Data format.
- Use Labels: With this option turned on, the data will use the column labels as tags instead of data column names.
- Error Email: An e-mail address that will receive an e-mail if the request fails after the number of retries is exceeded (5 days).
- Notification Email: An e-mail address that will receive an e-mail each time a request fails with a 400 or 500 level code and has not exceeded the maximum number of tries for Guaranteed Delivery.
- Guaranteed Delivery: With this option turned on when a POST request fails to reach the destination, it will be returned to a queue and will try again with the following schedule (1 minute, 5 minutes, 30 minutes, 6 hours, 24 hours).
- Request Time Limit: The amount time before a request times out. PLEASE NOTE: We recommend setting this to 60 seconds.
STEP 5. Click Create Endpoint.
PLEASE NOTE: With a dedicated database, you are able to post data to multiple endpoints. By allowing for more than one POST destination, data from records can meet multiple needs instead of just one.
Comments
9 comments
Security is the concern here. Are all these posts guaranteed to originate from the same IP address?
Your example appears to use port 80. Is iFormBuilder unable to post using SSL?
Hi Guy, the requests will not come from the same IP address as there are many servers which host the application. The example does show "http", but "https" is supported as well as long as the receiving server is setup for it.
How do we know what range of IP addresses to allow through our firewall? I assume this information is not published to the public.
Ideally you whitelist by domain and not an IP range because that can change over time.
The data security officers on our campus do not allow domain whitelisting because of the potential for dns poisoning. They only allow the whitelisting of ip address ranges.
Hey Rtims, you might consider having a server which sits between iFormBuilder and your campus network which acts as a pass through. This would allow you to whitelist the IP of the server you control outside the campus network, and ensures as the infrastructure scales the requests continue to come through.
Unfortunately, we don't have the budget to support additional servers.
Hey Rtims, AWS has a free tier that might be able to help you out. Worth taking a look if its just used as a passthrough.
https://aws.amazon.com/free/
Thanks for the info. I'll check into this.
Please sign in to leave a comment.