...

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.

...

If your submission had an error, you'll see an icon  in in the Err column in the submissions list. Hover over the icon to get information about the error.

...

To get more information, double-click on the submission to view its details, and again hover over the  icon icon.

If the mapped pdf has a severe mapping error such as (Invalid E-form field), the flow will submit and the pdf is generated. The submission is marked in error with  a  icon in the Submissions table. You will see the error: "One or more generated PDF forms generated with mapping errors.  Some information may be missing." on the submission.Image Removed

Image Added

Editing Submissions

...

Form/flow submissions are grouped by formid and uniquely identified by a submission id. Normally Normally,  allows you to instantiate from submission using the formtype or flowtype uri and the _submission parameter. The supplied _submission parameter value corresponds to the latest submission for that formid. If you are instantiating an older submission id, you  you see the following message: "Access Denied. This submission has already been processed".

The URL parameter (_override=true) allows the re-instantiation to happen even if the _submission does not correspond to the latest for the formid sequence. If you want users to see and potentially re-submit older versions, you will must append the _override=true parameter to the form/flow share link.

Let's say you want your non-designer users to be able to resubmit older versions of a form/flow.

1. The designer must grant view/edit permissions to the non-designer users via the Access Control feature. 

2. Append the override=true parameter with the submission id to the form/flow share url.

    The

    The designer user can locate the submission id by adding the submission - id column to the submissions table. 

       3. Copy  Copy the form/flow URL and append _submission=<ID ENTRY FROM FORM SUBMISSION TABLE>  - Here  Here is an example of the Product Order Form with the submission submission id, d310878f d310878f-94cc-41f6-ad4c-dd864b4fd513, which references an older submission.    

http://localhost:8082/frevvo/web/tn/doctenant/user/designer/app/_zQEN0Cx9EeSLmcVfjx9TOA/formtype/_QG3AIAxXEeSQ9sn0Gh0q3A/popupform?_submission=d310878f-94cc-41f6-ad4c-dd864b4fd513

...