How to turn on audit/history functions for Groups to be able to track changes made to groups

[Dinesh92]

How to turn on audit/history functions for Groups to be able to track changes made to groups, naming and description in particular.

[Dinesh92]

HI @Mark Roethof,

The requirement is that lot of changes happening in group naming and all i do understand that it is not right practice so how can we specifically restrict it to description and naming changes in particular.

Thanks.

[Mark Roethof]

" i do understand that it is not right practice"

Thats not true. Who says it's not right practice? You might be careful with this if all records receive daily an update through an integration for example, or then think of a way how to maintain the generated Sys Audit data.

If you need audit for a certain table, that can be perfectly fine, just have a good use case for it, just don't turn it on because you can. There are only a few tables which are really a bad practice (like wf_context, or em_alert).

It's just, DON'T enable audit for a full table, enable it for specific fields. That's the way it should be done nowadays, though most implementation partners or developers don't have a clue about this.

[Mark Manders]

Go to the dictionary and find the sys_user_group table. Select 'collection' and turn on audit. The question is why this is necessary. It will add extra audit records to your system.

[Dinesh92]

HI @Mark Manders 

The requirement is that lot of changes happening in group naming and all i do understand that it is not right practice so how can we specifically restrict it to description and naming changes in particular.

Thanks.

[Mark Manders]

As is written in this article:

When wanting to exclude specific fields from Audit for a table, you would open the Dictionary Entry of the specific Field and add an Attribute "no_audit". When wanting to include specific Fields to Audit for a Table, you would add to the Collection Dictionary Entry of the table an Attribute "audit_type=whitelist" AND open the Dictionary Entry of the specific field and add an Attribute "audit=true".  

https://www.servicenow.com/community/now-platform-blog/keeping-your-instance-database-footprint-tidy...