devdocs/specs/core-log-business.txt

@@ -1,11 +1,13 @@
 Business history log
 
 FROM CASE 79
-A central event log used to track changes to business objects and events of significance in AyaNova.
-??Has some sort of checksum or verification so we can tell it wasn't fucked with
+A central event log used to track major changes to business objects and major events of significance in AyaNova.
+??Has some sort of checksum or verification so we can tell it wasn't fucked with (too hard to implement, would be something like a blockchain?)
 Consumed by various widgets for record history purposes
 Default feature, no need to turn on or off keeps logs for 45 days, users who want more can 
 Items are only removed from log when source object is deleted (and replaced with a deleted entry and textual description of deleted item)
+Needs a cleaner job that periodically looks for non-existant objects that are logged
+Has to handle a scenario where there is no data for an object because in future we will likely have a purge feature or maybe a feature to turn it off and needs to accept that scenario
 
 
 EVENT_TYPES
@@ -42,6 +44,14 @@ USERID,
 TEXTRA (text field to identify stuff that can't be retrieved from source object, i.e. deleted record name) 
 
 
+DELETION
+--------
+The only way an entry is removed from the log is via deletion of the source object
+When a source object is deleted, the entire history for that object is removed from the log and a new entry is created showing the deletion and textual representation of the object
+    - The record has the object type so no need to redundently store that, just the name: "1234" for workorder 1234 or "ABC Accounting" for the client name etc
+
+
+
 TODO:
 1) Implement this log and routes to interact with it
 2) Implement an auto-prune job