You are viewing limited content. For full access, please sign in.

Question

Question

Feature Request: Save Draft Form for Logged In Users

asked on March 5, 2014

In forms there is currently the ability to allow someone filling out the form to save the form and complete it for later. This requires them to input their email address and a password and then a link is emailed to them.

 

I think that is great for Public users, but for users that are logged into Forms it would be great if when they select to fill out later that it saves it in a Draft section for them so they can simply log back into Forms and see their drafts without having to dig through their email and trying to remember a password to retrieve it.

1 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on March 10, 2014

Thanks for the feature request! We're currently researching ways to improve this feature. In a future release, we hope to make draft management a little easier for authenticated users.

0 0
replied on May 9, 2014

Is there any chance a feature like this will be included before 9.2? Even the ability to customize the email that is sent to the user that saved the form would do wonders for us. We have supervisors saving evaluation forms. They could end up with 30 emails saying they have saved a form, but no way of knowing which link is for what employee evaluation.

1 0
replied on May 9, 2014

9.2 will make saving a draft easier. I can't guarantee that this specific feature will be in there, but there is a chance.

0 0
replied on October 7, 2014

Forms 9.2 provides

1. Drafts visibility to authenticated users

2. Draft email customization per process

0 0

Replies

replied on March 6, 2014

Hi Blake,

 

I understand your frustration. I have had this requirement as well and have devised my own workaround for this.

 

You could have a "Save" button on the form that simply routes/assigns the form back to the same user when clicking on this button.

 

Initially, the only option you have when starting a form is to SUBMIT it using one button. I then automatically assign the form back to the current user, where they can then have up to 3 buttons to submit, save, reject the form. If they click on Save, then it just loops back to them. See the graphic below.

 

4 0
replied on June 11, 2014

Sheldon,  Your solution sounds interesting.  When the form is automatically assigned to them do they get an E-Mail and then they reopen the form and are presented with the three buttons you mentioned?

0 0
replied on March 6, 2014

Hi Blake,

 

As an interim workaround, you can also apply the methods described at the bottom of this post:

 

https://answers.laserfiche.com/questions/51439/Bypass-required-field

 

One of my colleagues, Farren, has created his own custom buttons that appears on any of the forms you design, even the initial starting form where you usually only have the option to Submit.

 

This also gives you more control on the Outflow of the form from step 1. Simply apply the concept I described above to reroute the task back to the initiator if they click on the Save button.

 

Regards,

Sheldon

0 0
replied on May 9, 2014

Just so I understand the concept here... I would create a workflow similar to what you have posted above. On the initial starting form I would include the following code as custom HTML:

<input class="saveButton" value="   Save   " type="Submit" formnovalidate="">
 <input class="submitButton" value="  Submit  " type="Submit">
 <input class="deleteButton" value="  Delete  " type="Submit">

And then this as custom JavaScript:

$(document).ready(function () {
    $('.saveButton').click(function () {
        $('.submit_Field input, .save_Field input, .delete_Field input').val("");
        $('.save_Field input').val("Save");
    });

    $('.submitButton').click(function () {
        $('.submit_Field input, .save_Field input, .delete_Field input').val("");
        $('.submit_Field input').val("Submit");
    });

    $('.deleteButton').click(function () {
        $('.submit_Field input, .save_Field input, .delete_Field input').val("");
        $('.delete_Field input').val("Delete");
    });
});

Is that correct?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.