I’ve put a data processor on GitHub for setting up the data history feature that arrived in the platform not long ago. Here’s what it does:
- Builds a tree of objects that support data history;
- Shows which objects currently have data history enabled;
- Lets you enable or disable data history for objects and their attributes.
It supports batch operations: for example, you can enable history for several documents and all catalogs at once. Or wipe all your changes and go back to the defaults the configuration developer set.
I think it turned out well. I mostly wrote it for myself, to give my brain a workout in the evenings, but we might even include it in our configuration! Right now, SSLi handles our data versioning, and it’s not exactly efficient: it’s slow and makes the database balloon. Hopefully, the platform will do better when we test it.
You can find similar tools on Infostart and ITS, but they’re either buggy, work only with Russian configurations (no English interface and dependencies on the Russian Standard Subsystems Library), or are just out of date, with no support for constants, for example.