Forms should be versioned #1499
Replies: 4 comments
-
|
Hiya @sussexrick, Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more. We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed). To open it this issue up again, you can write For example:
This will reopen the issue in the next few hours. Thanks, from your friendly Umbraco GitHub bot 🤖 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
@umbrabot still relevant In Forms 8.6.0 you can still lose data from earlier entries if you modify the form. |
Beta Was this translation helpful? Give feedback.
-
|
I would love to see this feature in Forms. It would be awesome to rollback to previous versions just like nodes in Umbraco. We just had a content editor that worked on a form for 2 hours, and saved the form every 20 minutes. With the last change made, hitting save froze the backoffice, and the latest version was somehow overridden with the version from 2 hours ago. Also the reason that @sussexrick had is a very valid reason to see this feature implemented. Hope to see this in the future! |
Beta Was this translation helpful? Give feedback.
-
|
This is still a very highly requested feature by all my ?Umbraco (Forms) clients today. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
First logged as http://issues.umbraco.org/issue/CON-1467 using Umbraco 7.6.12 and Forms 6.0.5.
What did you do?
Create a form and add some entries. Modify the form by adding, changing or removing a field. View the existing entries.
What did you expect to happen?
The existing data should be displayed alongside the questions it answered.
Aside from the simple issue that the data may accidentally deleted, or be misunderstood and therefore used incorrectly, if the form involves personal data and the legal basis for processing is consent - which will be a very common situation - then GDPR privacy law requires us to be able to prove what questions were asked and therefore what was consented to. We can handle this now by copying the form before making any changes, but that's a manual process that's vulnerable to human error.
What actually happened?
The existing data is displayed alongside the current form questions, which may not be the same. If a field was deleted, the existing data is lost.
Beta Was this translation helpful? Give feedback.
All reactions