The division "Activity" is great, but actually fails to give you a decent overview of recent activity. It needs slightly more info adding.

FYI - This item is slightly related to this bug, and will make more sense with consistent reference to "Activities" : https://prospectsoft.aha.io/ideas/ideas/SPABUG-I-716 

Under division (and contact, lead, etc), we have an "Activity stream" (UI group called Activity that lists notes and purports to give you an overview of recent activities with this division).

So, Ultimately i think you should be able to look at the activity for a division and get a good overview of what's happened in the last week or two. at the moment you can look at this list and not see any quotes/ orders nor any leads being logged or problems being logged or closed. So, i think that makes the activity stream fail in what it should be trying to achieve. 

We should add some more activities, and then auto-populate this stream whenever a user:

a) Automatically create an activity whenever a user creats a lead / problem / contact / quote / document - these are all activities against the division/contact/lead etc - as much so - if not more so - than adding a note.

b) Also, automatically add an activity when a lead/problem changes status, or a quote/order is processed (changes status)

c) And, when a contact/lead/problem is deleted.

d) record two activities (moved from, moved to) whenever a record is moved via a change parent

I think we should have specific "activity types" for these things, probably hard-coded that you cannot remove. and then effectively add a record to the "spokehistory" table whenever these actions take place.

I realise this crosses over slightly with change tracking, but it's not actually the same thing. I think in reality you want both, working totally independently (i.e. the history of changes will include all field changes, whereas the activity shouldn't, and record change tracking wont include each note added, whereas the activity list will).

I also realise that created & each status changes are already recorded in the record's created date and in lead/problem action logs. Again, i think this is a different thing and can be left alone, and the fact that some of that info is duplicated in the activity log isn't an issue. Obviously one alternative is to load all of this data independently into the notepad, but frankly that will be too slow, and you wont be able to report on it.