Auto-Save Patterns

I have an object table that displays data. Sometimes, users select data from the table and save it into an ontology object. When users later perform edits—such as deleting, updating, or adding more data—there is currently no automatic save mechanism.

At the moment, all changes are saved only when the user explicitly clicks a button in the UI, which triggers an action to persist the data into the ontology objects.

I’m wondering if there is an auto-save mechanism or recommended pattern that could be used instead of requiring users to manually click a save button every time.

There is no way to automatically trigger execution of actions from Workshop currently. I have made a note on an internal feature request with this signal.

2 Likes