...
Optionally Allow expiration of form versions based on a date that would be optional, I would appreciate how the wording of the message should be shown to a user trying to submit an expired form version would read.
Maybe a Valid from and Valid To date that the Submission could not be activated until Start DateMonitor the number of draft submissions in the wild in order to understand how many drafts exist. Knowing that there are 3000 version 2 submissions in a draft state might be useful before expiring a submission. If it is not expired then the mapping details for these may be important as the policies may have changed around the grant approval process.
Optionaly Instead add a period of days before the submission expires. This submission will self destruct in 10 days.
There are a couple considerations around scheduled forms, if there is also a closing date for the form then the messaging to an end user who has been told they have 90 days to complete a form would not work. As long as there is a closing date on the form and the expiration date on the submission is after the closing date then the closing date should be used on the edit of the draft as a message.
This form is scheduled to be closed on Feb 12, 2024