Good question!
For my current use case, whilst a beautiful UI to see audit trail would be amazing I suspect it is fairly complicated to consider the scenarios - and I would be fine with just being able to access the history via a downloadable audit log with
- submission id/uuid,
- name field from form,
- original value,
- new value,
- datetime change was made,
- changeid (if poss - so can collect all the changes made at that time - though could use datetime if needs be provided saved synchronously)
- user who made change
The audit log should also specifically show Validation status changes alongside all the content changes.
That way I could then join it back to the list of submissions and e.g. see all the changes made for a given district’s forms, or whatever identifier from the data that I want to group changes together by. Sometimes I’m looking at a specific submission’s history, other times I’m looking across multiple submissions (e.g. looking across a geographic area to find common issues that are requiring manual amendment at validation stage).
If additionally we could have a way of selecting a specific historic submission version to preview that would be great - though know that could cause complications when the forms themselves have been re-released in the interim.
Not sure if that is what you were after @tinok but those are my top-of-the-head thoughts
