Hi everyone,
We administer a domain separated instance of ServiceNow and do have many different requirements depending on the customer, one such recent requirement is to have the ability for a customer to write to their own assets. There is a grey line here from a business perspective as we manage this data but regardless, the business has decided to allow this.
To mitigate risk I plan on removing the no_audit attribute from most of the fields on asset but I am curious if anyone can give me some advice as to why alm_asset is setup this way OOB? 55 fields have the no_audit=true attribute and quite a high percentage of these I would suggest contain data that you would expect to want to track, I note most of these that are relevant in my situation are mapped between the asset and the ci field mappings.
Is it expected that each asset is managed by the associated CI record?
Appreciate all opinions on the matter, I'd be interested in what you may have done if you have come across the same situation.
Best Regards,
Brett
