Default dictionary attribute on table creation

Anton42
Tera Expert

Hello,

is it possible to have a collection of attributes automatically set up for the table collection during initial table creation?

So, I am creating a new table and I would like to have set up the attribute "no_audit_delete" for the table collection automatically.

 

So long...

1 ACCEPTED SOLUTION

I couldn't find anything OOB. From customization perspective there can be a BR (In my head, I haven't tried it, but logically it could be done with a custom script), but based on your answer you answer, you might want to go with something OOB?

Also, with all due respect to ServiceNow support (I find it depends on if the ServiceNow support personnel know what they are talking about, if I need to agree to what they say), If this is a requirement that you need to implement, I would go ahead and try to observe on my own as well.

 

Also, this property is what ServiceNow suggest, they should be assisting on this or updating the document. That is just what I feel. 

This is just what I think, up for a discussion further if you want 🙂

Please make it correct or helpful if this solves or help you with your issue for other to make use it.

Thanks & Regards,
Vikrant Sharma

View solution in original post

7 REPLIES 7

vikrantsharma
Kilo Guru

Hey Anton,

 

See if the below helps, here is the link to the page too:

Auditing system tables

By default, the system does not audit the deletion of a record from system tables. To audit a system table, add it to the list of tables in the glide.ui.audit_deleted_tables property list.

Auditing deletions from a form or list

By default, the system audits deletions of individual records from a form. To prevent auditing, set the table's dictionary attribute no_audit_delete.

The system audits deletions from a list when audit is selected on the table dictionary, and the table is not listed in the glide.db.audit.ignore.delete property.
Note: By default, the glide.db.audit.ignore.delete property is not present in the System Property [sys_properties] table. To change the property, and its associated values, you must first manually add it. However, when manually added, it overwrites the following default values:

glide.db.audit.ignore.delete = sys_mutex,sys_db_cache,sys_lucene_block,sys_lucene_file,sys_lucene_directory,sys_user_preference,sys_audit,sc_cart,sc_cart_item,sys_trigger,wf_context,wf_activity,wf_condition,wf_executing,wf_history,wf_log,wf_transition,wf_transition_history, cmdb_ci_windows_service, cmdb_sam_sw_install, cmdb_software_instance, cmdb_sam_sw_usage, sam_sw_counter_detail

Please make it correct or helpful if this solves or help you with your issue for other to make use it.

Thanks & Regards,
Vikrant Sharma

Hi,

that does not help.

We already found out with Support that the documentation is not precise and a lot of system tables are not named in the documentation. So, if any patch or upgrade is changing the list of tables, which should be in the property "glide.db.audit.ignore.delete", you only participate in that change if you don't modify the property manually.

Furthermore the support recommendation is to use the no audit delete attribute in table dictionary and not the property.

So, my question still remains: Is it possible to setup table attributes during table creation automatically? So, I press the create new button and the table is already created with the attribute "no audit delete".

I couldn't find anything OOB. From customization perspective there can be a BR (In my head, I haven't tried it, but logically it could be done with a custom script), but based on your answer you answer, you might want to go with something OOB?

Also, with all due respect to ServiceNow support (I find it depends on if the ServiceNow support personnel know what they are talking about, if I need to agree to what they say), If this is a requirement that you need to implement, I would go ahead and try to observe on my own as well.

 

Also, this property is what ServiceNow suggest, they should be assisting on this or updating the document. That is just what I feel. 

This is just what I think, up for a discussion further if you want 🙂

Please make it correct or helpful if this solves or help you with your issue for other to make use it.

Thanks & Regards,
Vikrant Sharma

Then I need to adapt the attribute after every update and upgrade manually, which is a useless manual step. And I need to trust the correct documentation which I don't currently. So, I would need to create a case every some month, which is also to time consuming.

I will play around with Business rules.