Central Auditing for Service Request Executions

4 votes

While we have "click history" for Self Service, we don't have any audit records that are centrally stored. Our Audit methodology at this point is database-centric so that applications don't have to audit... the database automatically "tracks" them. So it seems like there is a hole in that theory when it comes to Self Service.

Could we add a new Audit Category for "Service Requests", and then have audit triggers on the Service Request Execution history table? All we need to track is the user who clicked the button, date/time when they did it, and the name of the button. Then, even when click history is cleared out by Solution Manager, there is still an audit record for as long as customers want it (just like everything else in OpCon).

Collecting community feedback OpCon Suggested by: Hidden identity Upvoted: 09 Mar, '21 Comments: 0

Comments: 0