Discussions
MJF has an existing feature turned on in CHEFS called Save and Edit Drafts
This feature allows users of the Forms to Save a draft version of a Submission and come back to edit and finish the draft submission at a later date.
Problem: There is no current expiration of the draft, the user can come back years later and try to submit a version that is no longer valid from a policy perspective.
Submission versions can be older versions of the form.
My preference would be to not allow any edit of draft versions.
That being said it may not be likely that the business would enforce this request as it is useful to the end user not to be required to fill out a submission in one sitting.
The above being said leads to a couple issues if we allow draft submissions.
Mistakes that are published could exist for extended periods(no expiration) as draft submissions
Once there is enough volume of submissions it will be difficult to monitor the state of submissions being sent to Unity. A lack of quality information coming into the Unity system.
A couple ideas for mitigating this issue would be to
Optionally Allow expiration of form versions based on a date that would be optional, I will create a confluence document in CHEFS to describe the behavior but 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.