Should be fairly trivial (assuming only one or two fields are affected).
Add an additional Integer field to your object say status-update-count.
Create a rule with a trigger of “fields updated” and choose the status field. Action is to increment field value - choose status-update count.
Create a subset with predefined filter of status-update-count >= X on the object (where X is the count you need)
Create a rule with trigger event “Added to subset” on your new subset, that fires your event.
Create a second rule with same trigger event to clear down the update count if you want it to happen again…
Looks good to me - probably worth adding the count to some page somewhere initially so you can be sure it is being updated (and remove it once you are happy).
That’s tough. - You would need one counter per user per “Request for Evidence”. The only way you could do that would be to have a bridging object with a single field being the counter and you would need many 2 one relationships to both the user and the Request.
I am sure there is another way to do it, but the only ‘standard’ one that comes to mind is whenever you create a user you create a bridging object with a relation to all existing Requests - and similarly whenever you create a Request you create a bridging object to all existing Users - and I suppose when you delete a user, you delete all related bridging objects (and similarly for Requests! More than a few rules!
The other way would be with a custom event processor that created the bridging objects and relationships either as above, or only when a user updated the field the first time!
Don’t think I can see what is happening here. Can you create a list of Audit counter objects somewhere on a debug page and in include the count of the number of related users and the count of the number of related Requests - and check they match the number of users and number of requests on your system. I suspect you are creating a 1-to-1 to the audit object then a 1-2-many to the users If nothing obvious from that, then PM me with contact details and we can sort out a screen share next week.