Required Field Add-on Idea

@hopstudios also reminds me of Nep’s Mayhem presentation at EEConf

Yeah, this is basically exactly what I’m doing - but I do like the ‘enforced’ idea here.

One thing I’ve been secretly hoping for is the opposite - a toggle where you can EXCLUDE a revision from being saved, because you’re just fixing a typo or changing something inconsequential.

And then you’d want a way to disable that for a bank that needed EVERY revision saved. But yeah, I really like the idea overall of building out the revision functionality - as a third-party add-on.

The other half of the Mayhem presentation was the reminder/notification process that let entry “owners” know that it was time to review/update that specific entry. But the heart of it was a revision commenting system, so you knew what was done when to each entry.

@mithra62 The field side of this is a “logging” field - two connected text fields – one always empty, optionally required. The other, a concatenation of the first field and a date stamp, every time the entry is saved, optionally editable. Output would be the entire log as a single tag, or each line as a tag pair, with date and value. And maybe store the revision ID in it as well. I’d just make it a variant of a text field.

TPS Reports is a great name

Calling dibs on royalties