I agree , a brief explainer/demo video does a lot of convincing. Would you mind explaining your usecase ? I'd love to know if something can be accommodated in flowripple.
But what I really want is a workflow tool that integrates with low-code in the following way: as records come in, they are stored somewhere. There is an interface where a user can "claim" a record and then do their work on it. The workflow tool handles concurrency so that a record can only be claimed by one user at a time. The user either finishes processing the record and it moves on in the workflow, they discard their work and it returns to the original state so that it can be claimed again in the future, or they save their work so that they can come back and finish processing it later. There would need to be some kind of time out mechanism or a way to return a record to the original state.
The actual processing of the record happens using a custom interface that is built with low-code. So for text annotation, they land on a custom text-annotation interface when they claim a record.
Does that make sense?