From CollectiveAccess Documentation
On Save / Edit
i.e. when someone actively interacts with a record:
- conditions met (arbitrary expression)
- some use cases that could be covered by expressions (e.g. list item selected, ca_objects.status = completed) should be broken out as separate types for easy(-ish) use
i.e. a (daily/hourly/whatever) process has to check a set of records, or all records. Only available as digest.
- Loans / Checkouts due date (need some simple date math,e.g. due date minus 2 days)