Sometime you need to provide a link for an end user so that they can return to their form and edit a previously submitted record. You can do this by having them choose a login and password and using the login page in Respondent Update Mode. Or you can generate a URL that allows an end user to return and edit a previous submission without logging in.
This link can be useful to set up approval modes and to enable two step data collection.
Generate the Auto Login URL
The Integration Wizard generates this link for you.
- Launch the Integration Wizard for your selected Form by clicking Integration in the Form Designer toolbar.
- Click Next.
- Choose Direct Link and click Next.
- Choose Direct Edit Link and click Next.
- Copy the resulting URL from the LInk Code window to your clipboard for use later.
You need to include the link in an Autoresponder, Notification, Trigger, or PDF generated within Logiforms so that the LFUUID (a unique ID assigned to every record) can be parsed and replaced with the actual unique ID. The [LFUUID] value could also be replaced manually.
Autoresponders and notifications function as if it was a respondent update.
Example of a Two Step Data Collection Process
The URL you generate can be used, for example, to enable a two step data collection process. Suppose you allow a user to fill out the first page of a multi-page web form and then force the form to be submitted instead of advancing to the next page using a conditionally branching action. The URL generated above could be used within the Redirect URL of an autoresponder to redirect the user back to the same form, but this time they would be editing the previously submitted record.
Or you could append '&startPage=Page2' to the URL so that the user on page 2 of the form.
Auto Login In Embed Mode
The Auto Login to edit data can also be used in Embedded Integration mode, by passing the LFUUID=XXXXX in the param section of the embed code. This will bypass the login screen. This can be used even if the form does not have a username and password field. If no username and password exists, then the integration code needs to be manually updated:
mode : 'respondentupdate'
params : 'LFUUID=97c1b879-2660-47ab-bcfd-cbd39d0e9029'
Be careful when editing the integtation codeMake sure there is only 1 params attribute included in the integration code.
Restricting AccessAccess can be disabled for all records or via a rule using the Respondent Update Mode Security Settings. When disabled via the security settings, links used on secure workflows will still be accessible via a security token.