Add progressive form capability
Each iteration will be called a progression. Fields can be assigned to one or many progressions. Each time the form is submitted its in the next iteration. All non-interation fields will show up as read only with the data from the last iteration or if no data is there, no field at all. Each iteration’s submission date will be defined when sending out the form to begin with. After each iteration, the form will be marked completed so the values are set in stone before the next iteration. Use a cron to send out and monitor next iteration dates. Don’t use ad-hoc to ensure the form will definitely go out. Signature and sign date fields are all iterations by default and make sure they are not prefilled.
Log in to comment and vote
Comments2
Cameron Kolick
Mar 7, 2023
If a progression before the current one is not complete, cancel it. If a progression before the current one is deleted, allow the appropriate signers to fill out those fields as well as the current progression data. If it is a new submission and they date progression 1 and 2 as in the past, treat that as a second progression iteration and ask for 1 & 2’s data.
Cameron Kolick
Mar 7, 2023
Be sure that each progression is tied together so we don’t get duplicated data in reporting.