I noticed that Otto has new feature Table Triggers. What are the practical use cases for this?
You can send record updates to a webhook receiver. It’s like Window transaction, but works on the server. You can create audit logs or update records in another system.
Pretty sweet huh.
Strictly speaking this is an undocumented FIleMaker server 22.0.3 feature. It is what Studio uses.
We just expose a UI for it.
Todd
1 Like
So it seems that only one file / table can be monitored?
One table can be monitored with one trigger, to monitor multiple files and tables you would need to make a trigger per table/file combination.
-Kyle
Ok I see now - however it would be nice for the interface to see at a glance all the files table triggers that are enabled. I can see how things could be set and forgotten not realizing a file has a trigger.
@OceanWest its in the release notes for FMS 22.0.4 rtfm
If you want a quick overview the FMDiSC from Dec 12th, near the end will help
This is an async process as Todd says that it triggered from a data change in a record, some ideas:
lightweight audit log
notifications when record has been added manually
this interface is an affordance, you can easily query the GetAll end point to see what triggers are on a file yourself, including status and any unresolved queue items