Submission Data Extract Overview

   Journey Manager (JM) The transaction engine for the platform. |   Platform Developer |  All versions This feature is related to all versions.

Manager comes with the concept of submission's data extracts that allow a form builder to configure certain Maestro components so their user input can be extracted from the XMLXML (Extensible Markup Language) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. payload and then saved in an easy to read format, such as an Excel spreadsheet. This data extract can then be used for integration with external systems or distributed via emails for further processing. The Maestro editor comes with the Integration pane so you can easily configure component's data extracts and integration with Manager.

Submission data extracts usually represent only a subset of the form data, not all of it. To select which components are included in the data extract, you need to configure them either in Maestro or Manager.

Submission data extracts can also be used in:

• Collaboration jobs. You can pass information from a form to a collaboration job, for example, to customize email messages by taking the user’s first name and adding it to the email's greeting.
• Overlay receipts. Forms can be implemented as pixel-perfect receipts by using data extract values in AcroFormsAcroForms are the original PDF forms technology that accepts input in both Forms Data Format (FDF) and XML Forms Data Format (XFDF). Many 3rd party vendors support AcroForms..
• Card. A card is a repeating element in the form space, which can be customized from data in the form using data extracts.
• Form spaces' searches. You can use data extracts when searching form spaces. For example, you can search for a task that has been assigned to you by using the data extracts and not the entire XML file.

Form data extracts are a great way to quickly inspect key data elements in Manager and allow you to make business decisions or meet reporting requirements.

There are some best practices when using form data extracts:

• Do not extract Personally Identifiable InformationPersonally Identifiable Information (PII) is information about an individual that can be used to distinguish or trace an individual‘s identity, such as name, social security number, date and place of birth, mother‘s maiden name, or biometric records; and any other information that is linked to an individual. In Europe, PII is known as personal data., because it might be downloaded as a bulk CSVCSV is a comma-separated values fil, which s a delimited text file that uses a comma to separate values. A CSV file stores tabular data (numbers and text) in plain text. Each line of the file is a data record. Each record consists of one or more fields, separated by commas. file using Manager. Using data extracts in this way is not the intended design, rather it is used for reporting purposes for generalizing on a particular set of data, or testing. It is best to keep any PII out of the data extracts, and rather send this data to your secure back-end systems for processing.
• Do not extract every single piece of data in your form using data extracts. There are many other ways of integrating data into systems and sending your form data to your processing areas. Extracting all the data in your form using submission data extracts adds a level of development and ongoing maintenance overhead, which is not necessary given the many other options to retrieve your data.

Next, learn how to view submission data extracts.

Last updated on : 09 September 2019