Surveys instead of editing
Created: May 10, 2023 Updated: Oct. 5, 2026
In my current project nobody edits documents directly, every change goes through a survey.
I'm working on a GRC system, governance, risk and compliance, together with a CMDB that collects information about hardware and networks. The data is documents, and changes to them don't go through an ordinary edit form but through surveys, as they're called here.
There are several kinds of surveys and each covers a different part of a document. A filled-in survey doesn't change the data straight away, it goes through an approval cycle, and only after that does the change reach the document.
It reminded me of a system with record locking I worked on years ago. There a lock solved the problem of two people editing the same thing, while here there's no editing at all, there's a change proposal waiting for approval. Thanks to that, two surveys about different parts don't get in each other's way, and every change has an author and someone who approved it.
It's a bit like pull requests, only for data.
Machine-translated from Polish (original).