datenangebot
commented
10 months ago We discussed this for a long time and like to go this way.
My 2cents for this: Users need to be informed if something changes in a given table or view. It is specially useful to setup notifications on view, that way you can define what hints for what individual triggers are wanted. To build a flexible and expandable system we should integrate some triggers and actions into the flow system and avoiding to reinvent the wheel by finding an tables own "flow" system.
First ideas for triggers/events:
- CRUD actions performed on a table or view
- specific value changed, maybe with a individual filter (regex as this might for tech savvy's only?)
First ideas for actions: (notification actions might come from different apps, not part of tables but can be used here)
- Insert a new row with context and calculated values (context = data from trigger event -> table id, trigger name, ...)
- Update a specific value
Is your feature request related to a problem? Please describe.
Users often don't notice when someone added an entry to a table. It would be very helpful to have that as an option in "flow" so one could set up a custom notification or a talk message whenever something happens in tables.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response