During asset creation in "alm_hardware" table, Configuration Item field not populatingIssue In the "alm_hardware" table when creating a new Asset, a corresponding CI (Configuration Item) gets created and the CI name populates in the "Configuration Item" fieldBut in certain cases, the CIs get created but the Configuration Item field on "alm_hardware" field doesn't get populated for specific Models e.g. Windows Server, AIX Server, ESX Server CauseA custom Business Rule that was created in "cmdb_ci_server" table with filter conditions defined for specific Models (e.g. Windows Server, AIX Server, ESX Server, Linux Server) prevented the Configuration Item field from getting populated in "alm_hardware" table.ResolutionTroubleshooting: First create a Stack Trace Business Rule on "cmdb_ci" table following KB0683765Reproduce the behavior by creating a new Asset in "alm_hardware" table for the affected Model Category (e.g. "Windows Server")Analyze the Stack Trace Business Rule that was created from the System Logs to see what Business Rules get triggered along OOB (out-of-box) Business Rules AssetandCI & Create CI on insertIf there are any other Custom Business Rules found in the trace, disable them and try reproducing the behavior so that the Configuration Item fields get populated Note: If still on issues, needs further investigation.Related LinksIn this specific case, there was a Custom Business Rule named "Auto update fields based on servers" created on "cmdb_ci_server" table, which caused the CI field to not be populated in the "alm_hardware" table for the below Model Categories Windows ServerAIX ServerESX Server In order to resolve the issue, the problematic Custom Business Rule was disabled, and post reproducing the behavior by creating a new asset for the affected Model Category "Windows Server," the Configuration Item field got populated as expected