Hello:
Before I start, I have to say I LOVE some of the new features that arrived with Forms 10.4.4. The ability to skip or interrupt suspended tasks, as well as notification on suspended tasks, are HUGE improvements that will save us a ton of time! 
I know one feature I haven't had the chance to test from this upgrade was "...the ability for end users to be able to recover a failed form submission when there is a back-end error." Is the thought that this would eventually replace forms saving to a temporary location? We had occasionally used/referenced Temporary Forms to recover submissions that may not have saved properly (i.e. when a user had submitted something successfully), but I had noticed that this feature had been turned off on forms created more recently?
I had figured out modifying the is_savetolf field in the cf_business_processes record for the process from 0 to 1 would bring back the ability to save forms to a temporary location upon submission (for newer forms), but I wondered if the hope was to have this new feature replace this temporary save?
Please let me know if this might be the case, as I could still see saving temporary forms being a useful feature in the event the actual Save to Repository step might fail after the actual process is complete.
Thanks in advance for your assistance with this!
Marty Gaffney
Town of Okotoks
Question
Question
New Recover Failed Submission Feature vs. Saving to Temporary Location
Answer
The two features are actually unrelated. The new feature for recovering submissions will catch submission errors that would have failed before the instance was ever created. Previously, a user may have filled out and clicked submit on the form, but due to a couple of different reasons, the form would have thrown a submission error and lost all the data. Now, the submission data is recovered and placed back in the form, giving the user another chance to fix the issue and re-submit.
The other errors you are talking about are errors that happen after the form was successfully submitted and the instance is created. For instance, if the routing engine is down, the submissions will queue up waiting to be processed by the routing engine.
The is_savetolf field is actually a legacy option back before we had the save to repository service task. We used to have a process level setting for saving all submissions for a process into a specific repository folder. We took that out (and turned it off by default) when we added the save to repository service task that gives the designer control over what to save to the repository and at which step of the process. It appears you are modifying the database to try and tap back into legacy features that have since been superseded.
