What would keep the audit history tab from populating automatically on load?

Mark_Bailey
Mega Guru

When an asset is loaded in a form view, the audit history is not automatically populating. The rest of the related tabs load fine.

My asset team tells me it used to load automatically. I suspect something was adjusted during an upgrade to Geneva, by design or error unknown.

When you right click on the header and choose reload, the audit history tab will populate.

What would keep the audit history tab from populating automatically on load?

1 ACCEPTED SOLUTION

According to ServiceNow this is now new expected behavior. I find it odd, but OK.



ServiceNow says: "I did some more investigation and at the time the related list is first loaded the information it wants to display which comes from history line and history set is not loaded yet. That is why it works when you refresh or when you have the related lists load on demand which forces them to load after history line and history set are loaded. The behavior was mentioned in an old problem I found which was closed with no plan to fix so it is expected.



It doesn't happen when the old activity formatter is on the form because that would trigger the history line and history set to be loaded which explains the difference between Fuji and Geneva as the Geneva activity formatter works differently and loads after the related list if related lists are not set to on demand."


View solution in original post

4 REPLIES 4

Jon Barnes
Kilo Sage

is this a related list?   Only asking because I don't have an audit history tab on my personal instance, so assume this was a customization. Usually, any time I see a form not fully loading, it is because of a javascript error or malformed HTML, which can happen with journal fields.   Can you check your javascript console to see if there are any errors on the page.   would also be interested in seeing a screen shot of your form...


sergiu_panaite
ServiceNow Employee
ServiceNow Employee

Mark,



How are the related lists loading?



Screen Shot 2016-07-06 at 8.09.21 AM.png



If the related list load after the form loads, they will be loaded via AJAX and it must just be taking time to load the Audit History. What if you test by loading them either 'With the Form' or 'On-demand', does it shows any difference?



Regards,


Mark_Bailey
Mega Guru

Sergiu I had with form and changed to after form loads. Neither made a difference. When the form is pull up the list does not load, and then if you use the function reload form it will populate the related list audit history.



Jonathan it is a related list, however it is an out of box related list.



I copy the3 java console activity and don't see anything that jumps out at me, but I am not great with interpreting this.


Unloaded table does not match current table alm_asset


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 added render event for ui_policy_onLoad


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.543] form rendered


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 running inline scripts, count: 0


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 runBeforeRender


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.000] onLoad calcReturn


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.003] onLoad Asset tag not mandatory on cons/soft


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.000] onLoad Auditor - Set fields read-only


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.016] ui_policy loaded


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 runAfterAllLoaded, functions: 69


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 fireAllChangeHandlers start


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 fireAllChangeHandlers end


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 late load functions: 3


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.118] runAfterAllLoaded finished


alm_hardware.do?sys_id=af48afc…&sysparm_record_target=alm_asset&sysparm_rec…:99 +-- Parse times


alm_hardware.do?sys_id=af48afc…&sysparm_record_target=alm_asset&sysparm_rec…:100 | CSS parse: 142.41000000000008


alm_hardware.do?sys_id=af48afc…&sysparm_record_target=alm_asset&sysparm_rec…:101 | JS   doctype: 194.45500000000015


alm_hardware.do?sys_id=af48afc…&sysparm_record_target=alm_asset&sysparm_rec…:102 | JS at end of page: 313.8899999999999


alm_hardware.do?sys_id=af48afc…&sysparm_record_target=alm_asset&sysparm_rec…:103 +-- All parsing: 650.785


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 after page loaded starting


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.061] GwtListEditor onTableLoad, tables examined: 8


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.075] after page loaded complete, functions called: 7


js_includes_ngCommon.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:18505 >>> connection exists, request satisfied


angular_includes_1.4.jsx?v=03-23-2016_1452:110 >>> init alm_hardware?sys_id=af48afcea8c9a100a95bb0f7364435bd


js_includes_ngCommon.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:18505 >>> connection exists, request satisfied


js_includes_ngCommon.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:18505 >>> connection exists, request satisfied


angular_includes_1.4.jsx?v=03-23-2016_1452:110 >>> init alm_hardware?sys_id=af48afcea8c9a100a95bb0f7364435bd


js_includes_ngCommon.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:18505 >>> connection exists, request satisfied


js_includes_ngCommon.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:18863 >>>>>> /sn/rp/alm_hardware/af48afcea8c9a100a95bb0f7364435bd


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.166] *** WARNING *** GlideAjax.getXMLWait - synchronous function - processor: GlideSystemAjax


js_includes_doctype.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:10518   *** WARNING *** GlideAjax.getXMLWait - synchronous function - processor: GlideSystemAjax


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.378] *** WARNING *** GlideAjax.getXMLWait - synchronous function - processor: SysMeta


js_includes_doctype.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:10518   *** WARNING *** GlideAjax.getXMLWait - synchronous function - processor: SysMeta


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.310] *** WARNING *** GlideAjax.getXMLWait - synchronous function - processor: GlideSystemAjax


js_includes_doctype.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:10518   *** WARNING *** GlideAjax.getXMLWait - synchronous function - processor: GlideSystemAjax


js_includes_navpage15.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:1922 [00:00:00.301] *** WARNING *** GlideAjax.getXMLWait - synchronous function - processor: SysMeta


js_includes_doctype.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:10518   *** WARNING *** GlideAjax.getXMLWait - synchronous function - processor: SysMeta


angular_includes_1.4.jsx?v=03-23-2016_1452:110 factory.snPresence >>> server error @ Wed Jul 06 2016 09:15:52 GMT-0500 (Central Daylight Time)


js_includes_ngCommon.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:18863 >>>>>> /sn/rp/alm_hardware/af48afcea8c9a100a95bb0f7364435bd


angular_includes_1.4.jsx?v=03-23-2016_1452:110 factory.snPresence >>> server error @ Wed Jul 06 2016 09:16:07 GMT-0500 (Central Daylight Time)


js_includes_ngCommon.jsx?v=03-23-2016_1452&lp=Fri_Jul_01_08_46_31_PDT_2016&c=4_42:18863 >>>>>> /sn/rp/alm_hardware/af48afcea8c9a100a95bb0f7364435bd


angular_includes_1.4.jsx?v=03-23-2016_1452:110 factory.snPresence >>> server error @ Wed Jul 06 2016 09:16:22 GMT-0500 (Central Daylight Time)


angular_includes_1.4.jsx?v=03-23-2016_1452:110 factory.snPresence >>> server error @ Wed Jul 06 2016 09:16:37 GMT-0500 (Central Daylight Time)


According to ServiceNow this is now new expected behavior. I find it odd, but OK.



ServiceNow says: "I did some more investigation and at the time the related list is first loaded the information it wants to display which comes from history line and history set is not loaded yet. That is why it works when you refresh or when you have the related lists load on demand which forces them to load after history line and history set are loaded. The behavior was mentioned in an old problem I found which was closed with no plan to fix so it is expected.



It doesn't happen when the old activity formatter is on the form because that would trigger the history line and history set to be loaded which explains the difference between Fuji and Geneva as the Geneva activity formatter works differently and loads after the related list if related lists are not set to on demand."