The idea is:
I see that buttons are planned for columns inside Bika databases, that could be used to trigger automations. Which presumably would mean each row would have a button.
I think to expand on this, it would be nice if there were buttons/actions we could have that aren’t row specific but available from inside the database page (but not inside the database columns/rows themselves).
Sort of like this (but integrated nicely into the UI, outside of the table - rather than having to draw a button haha):
I’ve used the solution above for Google sheets as a convenient trigger for actions that involve several rows/columns.
I think this would be nicer for a lot of cases, compared to having a button for every record (which would be suitable for other cases though). Probably something like the ‘bulk update’ drawer but instead having a list of available actions/buttons.
My use case:
Basically, for partially automated processes. The case I’d like to cover is preparing payroll in Bika, automating where possible, then having a button/action somewhere that can trigger an automation to send everything required to a third party service via API once the data is ready. In this case, the Wise/Transferwise batch payments api: Can I automate batch payments? | Wise Help Centre