User reported a behavior that if the Nintex Form was left idle for some time (> 10 mins), the changes user entered on the form but not saved will be lost when user came back to form to click save button.
The sequence of user actions are
1. Edit Properties
2. Change Document Title
3. Doing nothing, and leave the form idle for 10 mins
4. Came back to the form, click 'Save' button
Now, instead of saving changes and close form, the form will refresh and remain open after been refreshed, but the changes will be lost.
Wonder if it is normal? any way to avoid it, as users not always complete the document properties at once, they would like leave the form open?
(Testing with a very simple Nintex Form in SharePoint 2013 env)
I have a distant memory of this being an issue for us too. This is related to timeouts in the Sharepoint environment and is not really anything to do with Nintex other than frustrating the users.
On your Sharepoint server, check the Session State timeout value in the Cookies settings section of the IIS for your site. Based on what you are saying, this will more likely be set to 10 minutes. Try something a bit more user-friendly like 30 mins or 60 mins and see if that improves the issue. You will need to perform an IIS restart for the changes to take effect.
Thanks for the reply. I will give a try, and let you know if it fixes the issue.
Did you solve your problem?
Here's a similar issue and its answer provides the way to solve it via PowerShell : nintex form time out