Does the button have triggers?
The buttons have action code without triggers. It executes when the button is pressed.
Is it possible to click a button in the insert row?
By default, no. But there are cases in which this is possible — they will be discussed later.
Can the button be executed remotely, by code?
Yes. Using the execButton function, you can press a button remotely.
And using execButtonList, you can sequentially press buttons in multiple rows that meet the condition.
How do I see the field logs?
If the field has the logging enabled parameter turned on, any manual changes to the field will record the time of the change, the user who performed the action, the entered value, and the final value.
If the logging enabled parameter is turned off, no logs are recorded.
From the context panel, right-clicking on the field provides access to these logs. This access can be restricted to certain roles using the log accessible to roles parameter.
If it was enabled and then disabled, the old logs will not be erased, but access to them will be lost. If re-enabled, access will be restored.
When is the action log recorded?
If the change is caused by an action code — for example, recorded through set, then to log the value, you need to specify the parameter log: true.
=: set(table: 'table:'; field: 'field' = #new_value; log: true)
Is it possible to record arbitrary text?
In the log, the action will be marked in the entered value as Script.
If you want to make a special note there, then pass its parameter log:
=: insert(table: 'table:'; field: 'field' = #new_value; log: "Successful payments")