"Enforce EAM category rules" Business Rule runs for alm_asset Asset Class, preventing valid inserts/updates to new and existing Model Categories - Known Error

"Enforce EAM category rules" Business Rule runs for alm_asset Asset Class, preventing valid inserts/updates to new and existing Model Categories Description The "Enforce EAM category rules" Business Rule for table Model Cateogry [cmdb_model_category] runs for alm_asset Asset Class, preventing valid inserts/updates to new and existing Model Categories. The business rule conditions suggest this should only run for asset classes in the EAM Model Class Hierarchy, which is table sn_ent_asset and the many extending tables from that.

This won't work:

Updating the out-of-box "Zones" and "Computer Room AC" Model categories. Creating a Model Category for alm_asset, either with or without a CI class Expanded Model and Asset Classes become a dependency of CMDB CI Class Models with 1.40.0, Oct 2022. This is a new app, but will install in Rome, San Diego and Tokyo. Upgrading CMDB CI Class Models to 1.40.0 or later causes Expanded Model and Asset Classes to be installed. Installing or upgrading an app that has CMDB CI Class Models as a dependency also upgrades CMDB CI Class Models would also causes it to be installed.

Steps to Reproduce

On a Rome, San Diego and Tokyo, upgrade CMDB CI class models to 1.40.1 or later. Or Utah, which has this out-of-box. Expanded Model and Asset Classes will get automatically installed as a dependency, and add the "Enforce EAM category rules" Business Rule

Open a Model Categories List a/ Updating the "Zones" and "Computer Room AC" Model categories, which are for asset class alm_asset. - Open "Zones" - Tick, "Enforce CI verification", and save - Errors, and update is aborted: Enterprise model and asset should belong to the same hierarchy of the parent category.Parent is empty Error MessageEnterprise model and asset should not be empty Error Message Model can not be empty for Enterprise categories Error MessageEnterprise model and asset can only be assigned to Enterprise asset and model classes respectively. Error MessageEnterprise model and asset should belong to the same hierarchy of the parent category. Error MessageInvalid update b/ Creating a Model Category for alm_asset, wither with or without a CI class - New - Enter: name: whatever CI Class: --None--, or select something Asset Class: Asset [alm_asset] - Save - Errors, and insert is aborted: Enterprise model and asset should belong to the same hierarchy of the parent category.Parent is empty Error MessageEnterprise model and asset should not be empty Error Message Model can not be empty for Enterprise categories Error MessageEnterprise model and asset can only be assigned to Enterprise asset and model classes respectively. Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.

It is possible to avoid issue by using one of the existing Child asset classes, such as Hardware or Consumable, or one of the many new Enterprise Asset Classes. Since Berlin, when the asset table was turned into an extended table, it's unusual to still be using the alm_asset table.

If you do have a requirement for model categories for Asset Class alm_asset, you can modify the script include EnterpriseContentEAMUtils.

change:

EnterpriseContentEAMUtils.inEAMAssetClassHierarchy = function (assetClassName){ return EnterpriseContentEAMUtils.getTableHierarchy(assetClassName).indexOf('sn_ent_asset') > -1; };

to :

EnterpriseContentEAMUtils.inEAMAssetClassHierarchy = function (assetClassName){ if (assetClassName == 'alm_asset') return false; else return EnterpriseContentEAMUtils.getTableHierarchy(assetClassName).indexOf('sn_ent_asset') > -1; };