WebDav (HTTP PUT) Data Destination

Available on the Advanced and Enterprise tiers:

Contents

• WebDav (HTTP PUT) Data Destination
  • About
  • Basic Set Up
  • File Configuration
  • Request/Response Configuration
  • Link the Data Destination to Forms
  • Testing and Troubleshooting Data Destinations

About

The WebDAV (HTTP PUT) Data Destination A Data Destination specifies where to send data from a submitted form. You can use Data Destinations to automate data sharing and storage, routing data to a specific service (such as email or cloud storage) in several different formats. sends data from submitted forms to systems that support the WebDAV technology. The standard use of WebDAV allows a server to act as a network drive, enabling collaborative work on files and objects contained in that folder. TrueContext WebDAV uses HTTP PUT, which allows users to:

• Create objects in an online collection or network drive
• Change or update objects in an online collection or network drive
• Move objects in an online collection or network drive

Most modern Operating Systems (OS) support some form of webDAV.

Data destinations automatically back up data collected in the field. They reduce the need to visit the web portal by making submitted forms available through the services you already use. Different documents can also be sent to different services with a single form submission. Read here for more information on data destinations.

Basic Set Up

1. Create the data destination following the instructions here.
2. Destination Basics: Name the destination. Optionally choose to auto-link forms and documents to this destination.
3. Add Filtering: With a filter set up, form submissions will only be sent through the destination if the filter is met. Read more here.
4. Connection: Set up an HTTP Connection or choose an existing connection.
5. Set up the File Configuration and Request/Response Configuration tabs as discussed below.

File Configuration

Send attachments in separate files, alongside the Data Record Document.

Optionally choose to send attachments (images, signatures, barcodes, etc) as separate files.

Folder Expression

This is the folder your documents will be sent to. If the folder doesn't exist yet, it will be created.

• Single folder: Enter the folder name. For a folder named "Inspections", enter "Inspections".
• Multiple folders: Use Data Reference Expression Language.
• %f - to sort submissions into folders named after the form.
• %u - to sort submissions into folders named after the user submitting the form.
• %a[Unique ID A Unique ID refers to the specific identifier of a question, form page, form section, or Data Destination. Unique IDs are used as reference points when pulling data for conditional logic, Analytics projects, Data Destinations, and Documents.] - to sort submissions into folders named with the answer to a chosen question. For more information on Unique IDs, click here.
• Optionally add static text for formatting - eg. "%f -- %a[Customer Name]"

Request/Response Configuration

URL Suffix

Enter the URL for the endpoint you want to send data to. You can use a DREL Data Reference Expression Language (DREL) is used to get form data and metadata and add it to a string, such as dates, usernames, or answers to questions in forms. expression to dynamically generate the URL.

Info:If you use a DREL expression to generate the URL, remember to escape the data you reference. This ensures that the system URL encodes the output generated by the DREL expression.

Optional Request Headers

Include any necessary request headers based on your third-party system’s API documentation specifications, except for authentication headers.

Note:Use an HTTP Connection to authenticate instead of Data Source Data sources, also known as "Lookups", are external sources of data that you upload or connect to TrueContext. You can reference this data in a form to populate answers or answer options. Data sources save typing, reduce errors, and make it easy to provide mobile users with only the relevant, most current data. or Data Destination headers. This keeps credentials and authentication values secure. The topic HTTP Connection includes a list of supported authentication methods.

Use the parameter builder to choose which individual answers to send as headers.

• Key: The name of the POST parameter that the destination will use.

• Value Expression: Use DREL to choose the data to send. Use the answer to a question by referencing a question's unique ID.

  Note:Answer values which are binary data (e.g. data from an image capture or signature) are base64 encoded.

HTTP Call Success Analysis

Select which HTTP response codes indicate a successful call. Optionally, you can use a Regular Expression to analyze the HTTP response body to determine success vs. failure. The Regular Expression results in success if the pattern is found anywhere in the body.

Link the Data Destination to Forms

In order for the destination to send any submitted form data, it must first be connected to the form. This is done in the Data Destinations tab of the form builder.

Testing and Troubleshooting Data Destinations

Data destinations should be configured and tested carefully before using them in production. This is key to ensuring that TrueContext data is received correctly. Please consult the recommendations for testing and troubleshooting data destinations.