Editing Form Submissions

 

 

About

ProntoForms allows your team to edit form submissions. There are two ways to initiate an edit: from the web portal, or in the mobile app.  All editing of form submissions is done in the mobile app. This feature makes it easy to:

  • correct errors that would impact downstream workflows,
  • allow mobile users to adjust forms if a customer changes their mind,
  • progress through a multi-stage workflow.

The ability to edit form submissions is configured at the form level, giving you control over which forms you want to allow your users to edit.

This article will discuss configuring a form to make use of this feature, how to send form submissions for editing, and important considerations for this feature's use.

[ top ]

  

Configuring a Form to Allow Editing of its Submissions

Before initiating any edits to submitted forms, you must ensure the Sent and Inbox tabs are enabled for your mobile users and for the desired form, then configure the form to allow edits to form submissions. Once you have enabled this setting, you will be able to edit forms submitted against the the new version of the form. It is not possible to edit form submissions made before these settings are enabled.

The ability to edit form submissions is configured at the form level, giving you control over which forms you want to allow your users to edit. You must be a ProntoAdmin or a User with Can Create permissions for the appropriate FormSpace to adjust this setting. To do so:

  1. Navigate to the appropriate form in the web portal and select Edit Form.
  2. Select the Settings tab.
  3. Select Allow form submissions to be edited beneath the Editing menu.


In all cases, only the original person who submitted the form can complete the requested edit on the mobile app. For more information on the types of permissions available in the web portal, please read: Permissions Overview.

From the Web Portal: ProntoAdmins and Users with "Can View" access to the form can send form submissions to mobile devices to be edited.

From the Device: If enabled on the form, mobile users can initiate edits to form submissions in the app. 

 

[ top ]

  

How to Send a Form Submission for Editing

There are two places that a form submission can be sent for editing: the web portal and the mobile application. 

Initiate an Edit in the Web Portal

ProntoAdmins and ProntoUsers with Can View permissions can send the previously submitted form to the original submitter for editing using the web portal. 

To send an edit request for a form submission from the web portal:

  1. Navigate to the Data tab in the web portal.
  2. Select the appropriate form submission.
  3. From the dropdown menu next to the form submission ID, select Send for Edit. This will send the form submission back to the original submitter's inbox and notify them via push message.


  4. In the popup box, add any required notes to the request. These can be notes on what needs to be edited, instructions, an approval, or even the next step to take in the task. Select Send.


    Note: Notes are limited to 256 characters. Notes will be applied to the latest version of the form submission, not the existing one. They are not cumulative. Each form submission version has its own notes (if supplied).

[ top ]

 

Initiate an Edit from the Mobile App

If correct permissions are enabled, mobile users can choose to edit their own submissions through the mobile app. To send an edit request for a form submission from the mobile device:

  1. Navigate to your Sent screen in the mobile app. 
  2. Tap and hold the form submission you want to edit. This will send it back to your Inbox.


  3. Navigate to the Inbox and select the form you requested to edit.


  4. Complete your edits, then hit Send as normal.

[ top ]

 

Sample Workflow

This sample workflow uses the web portal to send the form submission for editing. Through the entire workflow, the Data Record ID will remain the same.

  1. A mobile user fills out a form (in this case, a vehicle inspection form) as normal, with one or two missing answers and submits it. It shows up in the mobile app's Sent folder as normal.
    2017-03-17-EditDR01.png

  2. A ProntoAdmin reviews the submission and finds it needs to be corrected. They select Send for Edit and highlight the problems in the form submission by adding Notes to the request. The request's time is recorded in the form submission's status information and the status changes to Complete (Sent for Editing).
    2017-03-17-EditDR02.png

  3. The mobile user receives a push notification and checks their Inbox. The submitted form is there, tagged with the Notes and marked Edit Requested. They perform the edit and re-submit the form.
    2017-03-17-EditDR03.png

  4. The ProntoAdmin refreshes the form submission page.
    • Edited fields are highlighted by Edited next to the new data:

      Note: This compares the two most recent versions of the form submission and marks any changes as Edited. It is not a cumulative review of all edits.

    • The form submission is marked Complete (Edited):
      2017-03-17-EditDR04.png

 [ top ]

 

Important Considerations

It is important to keep the following in mind when enabling this feature for forms:

Inability to Decline:

Forms sent for editing are unable to be declined, unlike standard dispatches.

Geolocation and Time Controls:

  • The Geo Stamps and Timestamps from the original form submission will be retained.
  • If the questions are Geo Controls or Date/Time Selectors and the user interacts with them, the original values will be overwritten.  

Changing Data:

When enabling this option, consider the potential effects, e.g., if a mobile user changes a price on an invoice after a customer has signed the form, it can change the validity of the data. We do not recommend allowing editing in forms that require customer sign-off unless the customer is present to sign the updated copy, for example. 

Unsupported Data and Control Types

Some data and control types will not work when editing a form submission. Avoid using this feature with forms using these types of questions. They are:

  • Audio
  • File Upload (this functionality is coming soon)
  • Barcode
  • Credit Card Transaction

Dispatch Destinations

We do not advise using this feature with the Dispatch Data Destination, as the dispatch destination re-executes with each edit to the form, creating a new dispatch each time the form submission moves into a "Complete" state. Instead of overwriting the original data and maintaining the same Data Record ID, it creates dispatches containing each iteration of the data.

 [ top ]

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments