Once a user has authenticated a first time they will not have to authenticate again until their browser session expires as a cookie is maintained. If the user clears browser cookies or opens the form in a different browser they will have to re-authenticate.
As a form designer you can also use the save/load feature for testing purposes. Since the Form Server has already authenticated you when you logged into , the save/load authentication dialog will never be displayed.
Saved forms are not the same as submitted forms. Saved forms and the user who has the form locked can be viewed in theby checking the SAVED checkbox as the submission type . Saved forms can contain invalid data and also contain required fields with no values yet entered. When such a form is re-loaded the missing and invalid values are again flagged as such by . And the form cannot be submitted until corrections are made to those fields.
The Save Button Label can be customized for each step in your workflow. For example, you can change the button text to Save for Later on step 1 of your flow and then to something different on step 2. This will help users understand what to do if they want to save a partially completed flow. Designers should click here for the details.
Currently the ability to change the Save button label is only available for flows.