<h2>If an update is done on the CI, and the AssetAndCISynchronizer synchronizes the fields on the asset, are these updates logged in the audit log?</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Issue </h3><section><style type="text/css"><!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } </style> <div class="ns-kb-css-body-editor-container"> <p style="padding-left: 40px;">If an update is done on the CI, and the AssetAndCISynchronizer synchronizes the fields on the asset, are these updates logged in the audit log?</p> <span id="ns-kb-css-end-div-identifier" style="display: none; pointer-events: none;"></span></div></section></div><div ><h3 >Release</h3><section><style type="text/css"><!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } </style> <div class="ns-kb-css-body-editor-container"> <p style="padding-left: 40px;">Any Release</p> <span id="ns-kb-css-end-div-identifier" style="display: none; pointer-events: none;"></span></div></section></div><div ><h3 >Resolution</h3><section><style type="text/css"><!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } </style> <div class="ns-kb-css-body-editor-container"> <ul style="list-style-position: inside;"><li>No — when a CI is updated and the AssetAndCISynchronizer copies values to the Asset, those field updates are NOT written to the Asset's audit log.</li><li>This is expected behaviour because the sync runs programmatically and silently, not as a user or audited update.</li></ul> <p style="padding-left: 40px;">Asset ↔ CI synchronization is not a "normal update"</p> <p style="padding-left: 80px;">The synchronization between:</p> <ol><li style="list-style-type: none;"> <ol style="list-style-position: inside;"><li>cmdb_ci_peripheral</li><li>alm_asset</li></ol> </li></ol> <ul style="list-style-position: inside;"><li>Is handled by the AssetAndCISynchronizer (script include + scheduled / event-driven logic).</li></ul> <p style="padding-left: 80px;">This sync:</p> <ol><li style="list-style-type: none;"> <ol style="list-style-position: inside;"><li>Runs in the background</li><li>Uses setWorkflow(false)</li></ol> </li></ol> <p style="padding-left: 80px;">Bypasses:</p> <ol><li style="list-style-type: none;"> <ol style="list-style-position: inside;"><li>Field audit (sys_audit)</li><li>Business rule activity logging</li><li>User attribution</li></ol> </li></ol> <ul style="list-style-position: inside;"><li>So even though the Asset record changes, ServiceNow does not consider it an auditable user update.</li><li>Can these sync updates be audited?</li></ul> <p style="padding-left: 80px;">Out-of-the-box<br />No. ServiceNow intentionally avoids auditing sync writes to prevent:</p> <ul style="list-style-position: inside;"><li style="list-style-type: none;"> <ul><li style="list-style-type: none;"> <ul style="list-style-position: inside;"><li>Audit noise</li><li>Performance degradation</li><li>Infinite sync loops</li></ul> </li></ul> </li><li>Why does ServiceNow do this?</li></ul> <p style="padding-left: 80px;">From a platform perspective:<br />Asset ↔ CI sync is a data consistency mechanism</p> <ul style="list-style-position: inside;"><li style="list-style-type: none;"> <ul><li style="list-style-type: none;"> <ul style="list-style-position: inside;"><li>Not a business action</li><li>Auditing every mirrored update would:</li><li>Double audit volume</li><li>Reduce performance</li><li>Create misleading change history</li></ul> </li></ul> </li><li>So ServiceNow expects customers to: <ul><li style="list-style-type: none;"> <ul style="list-style-position: inside;"><li>Audit source tables</li><li>Not synchronized targets</li></ul> </li></ul> </li></ul> <span id="ns-kb-css-end-div-identifier" style="display: none; pointer-events: none;"></span></div></section></div></article></div>