comes with a built-in submissions repository. The repository can run on top of most SQL databases. By default, your form data is stored in the repository and can be viewed from the Submissions page.

Filter your submissions using form data. Create Logical expressions to narrow the search for particular submissions. Fields in your form/flow, set up as Searchable fields by the designer, can be used as criteria when searching submissions. Once your Searchable fields are defined,  re-indexes existing submissions so you can search them using the same fields.

Additional default fields such as: error, error description, submitter id, lock user id, started date, etc. can also be selected as filters.

The Submissions view works well on mobile devices and is easily embedded in a web page and wikis such as Confluence. Customers running with Confluence will not see the legacy submissions view from the Confluence Screen. It is only available when you log into your Confluence tenant.

The /wiki/spaces/frevvo82/pages/767365384 and the/wiki/spaces/frevvo82/pages/767365315 must be running for the Submission view to work.

Cloud customers will see an icon for the Submission View and another icon for the Legacy submissions view. The /wiki/spaces/frevvo82/pages/767365315 topic discusses the ability to hide the Legacy view among other options for in-house customers. 

The Export of submissions to Excel feature has been replaced by the Download to CSV. If you have not used the Export to Excel feature in the past, we recommend that you become familiar with the Download to CSV .

You can still use the Export to Excel feature by accessing it from the Submissions Legacy view. However, the Legacy Submissions view and the Export to Excel may be removed in a future release.

The various items on the Submissions page are explained below.

On this page:

Accessing Submissions

To access submissions for a particular form/flow, the designer who created the form (owner) navigates to the Forms Home Page or the Flows Home Page and clicks the  Submissions icon for that form or flow. The designer can grant permission to view/edit submissions to other designers and non-designer users/roles via the Access Control feature. Non-designers granted view/edit permissions, access submissions from the Shared Items tab.

A Shared Items link is added to newly created Spaces automatically and can be added to existing spaces.

Searchable Fields

Searchable fields can be used as search criteria for submissions and tasks. They also define the fields that will be displayed and exported in the export to a csv file.

Once defined,  can also go back and re-index your existing submissions so you can search them using the same fields.

Submissions View

When you click the Submissions icon a Submissions view consisting of two sections displays:

1. Submissions filter section
2. Matching submissions results table.

Initially, the Submissions Filter section is collapsed. Click on the blue arrow to expand it.

Submissions Filter

The Submissions filter section contains:

• Section A - From Date and To Date fields to specify a date range.
• Section B - Check the status of the submissions you are searching for
• Other Filter Items section - setup your search criteria, including the capability to edit the logical expression used as the search criteria.
• Reset button - To start over with a new set of filter criteria, click the Reset button. This will clear all criteria, including the from/to dates, state and all rows of the other filter items.
  
  
  
  When the expression or any of the sub-expressions change in any way, the submissions query is automatically re-run and the results are updated in the Submissions Table.

Submission From Date and To Date

The two date controls specify the time period for the submissions you see. The dates default to the current date and one month earlier, so you see one month of submission results when the Submissions page first displays.  Adjust the dates if you want a shorter or longer time period.

Submission Status

The Submissions table will show submissions in the following states: SUBMITTED, SAVED  PENDING, ABORTED, ERROR and WAITING. Simply check the appropriate check box in the State section. For example, It would be easy for a manager to check  the current status of Expense Report approvals by checking one or all the submission types in the State box. The Submission Table dynamically changes as the submission state choices are checked/unchecked.

Here is an explanation of the available states:

1. SAVED/PENDING: This will give you all the tasks which are saved or pending. This helps when you want to see all open tasks for a certain form/flow
2. SAVED: This will return only those tasks which were created when users clicked the Save button on the form/flow to save their partially filled forms
3. PENDING: This will return all tasks which are pending, meaning someone else put these tasks in the users task list
4. SUBMITTED: This will return all tasks which are completed, i.e. the form/flow for which this task was created has been submitted
5. ABORTED: This will return all the tasks that were deleted/aborted so the form/flow never got submitted
6. WAITING: The WAITING status can be used to find workflow tasks that have an Email or HTTP activity. A submission will show a state of WAITING  when a workflow is routed to an anonymous user and the flow is suspended until the this step is completed.

Choose Search Criteria from Form/Flow Data

The Other Filter Items section describes the conditions that submissions must match in order to be included in the Submission Table. Here is how the grid works:

• Click the plus / minus icon to add/remove rows. Rows are labeled numerically beginning at 1 and are color coded. You can specify up to 100 rows of filter criteria.
• Specify the field, condition and value for the search criteria you are adding. For most conditions, all three columns are required but there are some that may not require a value. 
• As you add fields and conditions, they are automatically added to the logic expression field by appending an "AND" and the character of the sub-expression (A for the Date section, B for the State section or the number of the row in the filter table as appropriate). Each sub-expression is color coded for quick reference. The characters for the sub-expressions are also color coded to match the row in the grid where the expression is defined.
• Click the Edit button to modify the logic expression.
• Click the Reset button to clear all of the search criteria.

Let's take a closer look at the columns in the Other Filter Items grid.

Field Column

The Field column includes a dropdown where you can select any fields that were specified in the Searchable fields wizard in your form/flow or you can choose from default columns that are available across all form and flow types. 

Condition Column

The Condition column choices depend on the data type of the selected field. Click below to see a list of the data types and their corresponding options.

For example, the choices in the Condition dropdown, will be different if you select the Submitted Date or the ProjectName, which is a searchable field in the form/flow from the Fields list.

Value Column

The values entered into the Value Column depend on the field type and also sometimes upon the condition chosen. Click below to see a table of the allowed values for Field Type(s) and conditions.

For Example, if you select a Date field, the Date Picker is provided to help enter the value. If you select a Text field from your form/flow, you will be prompted to "Enter text" for the value. If you select the Error metadata field, the value choices will be True or False in a dropdown in the Value column.

A Date/Time field with the "is within last" condition selected, requires a special time duration entry. The duration must be entered in this format: Years:Months:Days:Hours:Minutes. Fields to the left may be omitted. For example, if you were searching for submissions that were submitted within the last 2 hours you can enter 02:00 or as 2:0. To search for submissions created within the last 2 months and 12 days, enter 02:12:00:00.

If you enter an invalid value, an error will display with instructions: 

Editing the Logical Expression

If you want to modify the logical expression, click the Edit button. The logic expression becomes editable.

The Logic Expression allows you to customize and combine the filter conditions using ANDs and ORs as well as parenthesis () to group terms of the expression.

• Each filter item (expression) is represented by a letter (A for the Date range or B for the State or a number that corresponds to the row of the sub-expression in the Other Filter Items grid).
• Combine the letters and numbers using parenthesis to group items as needed.
• Build the logic of the overall predicate expression using AND and OR as appropriate.
• Click save when done to save the expression. Please correct any indicated parse errors in order to save.

For example, let's say you have a Job Application that has 3 submissions:

You want to display the submissions that were submitted on November 7, 2016 or any of the applicants that live in Connecticut (Home Phone Area Code is 203):

• Expand the Submissions Filter.
• Select the SUBMITTED state.
• Select the Acknowledgement Date field from the Fields dropdown
• Select "is equal to" from the Condition dropdown.
• Use the Date Picker to select "11/7/2016" as the value.
• Add a row to the Other Filter Items grid.
• Select the Home field from the Fields dropdown.
• Select "begins with" from the Condition dropdown.
• Enter "203" as the value.

At this point, the expression displays only one submission that has an Acknowledgement Date of 11/7/2016 AND has a Home Phone number that begins with an area code of 203.

This is not the expected results. To display the submissions that were submitted on November 7, 2016 OR have a Home Phone number that starts with an area code of 203, the logical expression has to be modified.

• Click the Edit button.
• Change the expression to A AND B AND (1 OR 2)
• Click the Save button.

The submissions that match the Date range and State conditions and either were submitted on November 7, 2016 OR contain a Home phone number that starts with an area code of 203:

Upon selecting the Save button, the logic expression is parsed for correctness. If there is any parsing failure, an error message describing the failure is displayed and the screen remains in edit mode. If there is no error, then the screen returns to read-only mode.

Recap

In summary, let's say Jerry, a manager wants to create a submission query to check the status of all Expense Reports for Sales Demonstrations performed by the Sales department within the last month:

• Make sure you have a field in your Expense Report to specify the Project Name - for example, a dropdown with Infrastructure, Sales Demonstration and Customer Meeting options.
• Make sure Jerry has been granted permission to view submissions in the Access Control List for the Expense Report workflow.
• Create a Space and distribute the link to the Space to Jerry
• Jerry access the Space and logs into .
• Jerry clicks on the Important Items tab in the space.
• Jerry clicks on the Shared Items tab.
• Jerry clicks the Submissions tab for the Expense Report workflow.
  
  
  
  
• On the Submission Filter screen, Jerry selects:
  
  • The Project Name field from the Fields dropdown
  • The contains condition from the Condition dropdown.
  • Types "Sales Demonstration" in the Value column.
  • In the Submission Table, Jerry can quickly see that Ricard Walker has saved an Expense Report for a Sales Demonstration to his Task List, Maria Myers has an Expense Report for a Sales Demonstration pending approval and an Expense Report for a Sales Demonstration was completed for Deborah Morris.
    
    

Submissions Table

Submissions matching the submission filter are displayed in the Submissions table. The table has the following features and behaviors:

• The results are displayed a page at a time. The Previous, Next page buttons  and individual page links, located in the lower right