[Xanadu] "Update last used date" Business Rule on Asset(alm_asset) table causing Performance Issues on update on asset records DescriptionThe business rule "Update last used date" on the alm_asset table is configured to run After update and includes a current.update() call. Since it executes during an active update transaction, this causes a recursive update scenario. As a result, warnings appear in the logs, and the update is ignored. This can lead to performance degradation and possible data loss. The issue is introduced with Asset Management Common [sn_itam_common] version 10.1.0, which adds this rule when upgrading from earlier versions.Steps to Reproduce Use a WashingtonDC instance.Install Hardware Asset Management [sn_hamp], which also installs: -> Asset Management Common [sn_itam_common] v10.1.0 -> Physical Assets [sn_phy_assets] v2.1.0If HAM is already installed with an older version of sn_itam_common (e.g., 9.0.0), upgrading to 10.1.0 introduces the business rule. Check the script at: /sys_script.do?sys_id=89f27f2e7795b11087d92531df5a99dc Observe that the script runs After and contains:(function executeRule(current, previous) { current.cmn_last_used = new GlideDateTime(); current.update();})(current, previous); Appnode logs show a warning like:Recursive business rule call for 'Update last used date'... is being ignored.WorkaroundThis problem has been fixed. If an upgrade is possible, please refer to the Fixed In section to determine the latest version with a permanent fix that the instance can be upgraded to. Upgrade application Asset Management Common (App id: sn_itam_common) to v12.0.0 or later. The issue was resolved by changing the business rule to run Before instead of After and removing the current.update(); line from the script. This ensures the cmn_last_used field is updated as part of the current transaction without triggering a recursive update. The fix improves system performance and prevents unnecessary warnings. A permanent resolution is included in Hardware Asset Management version 11.0.1 under PRB1786776, and applying this patch is recommended.Related Problem: PRB1786776