Hello,

When a case is locked, it produces an audit event with EventClassId: resource:103 (name: Case Locked). Same goes with case unlocked, which is audit resource:104 (name: Case Unlocked)

At the same exact time, an audit event resource:101 (name: Case updated), which is the most important one, because subsequent edits or notes while the case is locked produce this.

Do you know of any method, to avoid firing a resource:101, when an case lock/unlock happens?

reason: We use the Case Updated as a trigger to inform our MSS Customers that a case has been updated, but having this event for every lock/unlock produces to many notifications.

ps: Of course there can be workarounds for our business case, I am just interested if this is system-configurable.

Thanks