Expanded Model and Asset Classes - Best Practices for Managing in ITSM Pro without EAM

jared_rlc
Tera Contributor

Issue: "Expanded Model and Asset Classes" (sn_ent) Plugin Installed in ITSM Pro Without EAM

 

Background: Currently running ITSM Pro without the Enterprise Asset Management (EAM) plugin. At some point, the "Expanded Model and Asset Classes" plugin (sn_ent) was installed in the instance. Unfortunately, these Asset classes appear unusable when creating new Assets. However, these EAM Model Categories can be used when creating new Models and Model Categories.

 

Steps to Reproduce

 

  • Install sn_ent (“Expanded Model and Asset Classes”).
  • Create a Model Category under an expanded sn_ent_* Asset Class.
  • Create a Product Model using that category.
  • Attempt to create an Asset using the model/category.

 

Result: The new model/category can't be selected during Asset creation since ITSM Pro’s asset interceptor filters out Expanded Asset classes.

 

That leads me to ask:

 

  1. Why is this plugin available for install without EAM?
  2. Now installed, how do you best configure ITSM Pro to manage these unusable Expanded Asset Classes?
    1. It seems to me that these Expanded Models and Asset Classes are likely to become problematic in a transform or confuse Asset Managers who think they can be readily used.

 

Appreciate your thoughts,

Jared


FYI, here are the installed tables as part of sn_ent:

Spoiler
LabelNameExtends tableExtensible
Information Assetalm_information_assetAssetTRUE
Information DNS Assetalm_information_dns_assetInformation AssetFALSE
Enterprise assetsn_ent_assetAssetTRUE
Commercial lines insurance product modelsn_ent_b2b_ins_policy_modelService ModelFALSE
Personal lines insurance product modelsn_ent_b2c_ins_policy_modelService ModelFALSE
Cable modelsn_ent_cable_modelEnterprise good modelTRUE
Card service modelsn_ent_card_service_modelService ModelFALSE
Construction assetsn_ent_construction_assetEnterprise assetTRUE
Construction modelsn_ent_construction_modelEnterprise good modelTRUE
Deposit modelsn_ent_deposit_account_modelService ModelFALSE
Discovered firmware modelsn_ent_discov_firmware_modelDiscovered SW component modelFALSE
Drug modelsn_ent_drug_modelMedical modelTRUE
Facility assetsn_ent_facility_assetEnterprise assetTRUE
Facility modelsn_ent_facility_modelEnterprise good modelTRUE
Financial service modelsn_ent_financial_services_modelService ModelFALSE
Firmware modelsn_ent_firmware_modelSoftware component modelFALSE
Group life insurance product modelsn_ent_group_life_ins_policy_modelService ModelFALSE
Individual life product modelsn_ent_indiv_life_ins_policy_modelService ModelFALSE
Industrial assetsn_ent_industrial_assetEnterprise assetTRUE
Industrial modelsn_ent_industrial_modelEnterprise good modelTRUE
Investment modelsn_ent_investment_modelService ModelFALSE
Line of credit modelsn_ent_line_of_credit_modelService ModelFALSE
Loan modelsn_ent_loan_account_modelService ModelFALSE
Logical network connection modelsn_ent_logical_nw_connection_modelNetwork modelFALSE
Medical assetsn_ent_medical_assetEnterprise assetTRUE
Medical device modelsn_ent_medical_device_modelMedical modelFALSE
Medical insurance modelsn_ent_medical_insurance_modelService ModelFALSE
Medical modelsn_ent_medical_modelEnterprise good modelTRUE
Medication modelsn_ent_medication_modelDrug modelFALSE
Enterprise good modelsn_ent_modelProduct ModelTRUE
Enterprise model classificationsn_ent_model_classification FALSE
Enterprise model classification sourcesn_ent_model_classification_source FALSE
Enterprise model classification typesn_ent_model_classification_type FALSE
Network topology modelsn_ent_network_topology_modelTopology modelFALSE
Network card modelsn_ent_nw_card_modelNetwork modelFALSE
Network equipment modelsn_ent_nw_equipment_modelNetwork modelFALSE
Network holder modelsn_ent_nw_holder_modelNetwork modelFALSE
Network interface modelsn_ent_nw_interface_modelNetwork modelFALSE
Network modelsn_ent_nw_modelHardware ModelTRUE
Permit modelsn_ent_permit_modelContract ModelTRUE
Physical network connection modelsn_ent_physical_nw_connection_modelNetwork modelFALSE
Retail assetsn_ent_retail_assetEnterprise assetTRUE
Retail modelsn_ent_retail_modelEnterprise good modelTRUE
Social benefit modelsn_ent_social_benefit_modelService ModelTRUE
Strand modelsn_ent_strand_modelEnterprise good modelTRUE
Tactical equipment assetsn_ent_tactical_assetEnterprise assetTRUE
Tactical equipment modelsn_ent_tactical_modelEnterprise good modelTRUE
Topology modelsn_ent_topology_modelProduct ModelTRUE
Transportation assetsn_ent_transportation_assetEnterprise assetTRUE
Transportation modelsn_ent_transportation_modelEnterprise good modelTRUE
Vaccination modelsn_ent_vaccination_modelDrug modelFALSE
Wearable assetsn_ent_wearable_assetEnterprise assetTRUE
Wearable modelsn_ent_wearable_modelEnterprise good modelTRUE
1 REPLY 1

jared_rlc
Tera Contributor

My team ended up resolving this by creating a custom “Create New Asset” catalog item with a dedicated Flow, rather than relying on the OOB asset form.

Highlights:

  • Abstracted complexity – Users interact with a simple Service Catalog form that gathers the required fields (including manufacturer, model, and category), instead of navigating the full Asset form and needing to understand which records do what and why.

  • Inline creation of related records – The Flow allows users to create Models and Manufacturers on the fly if they don’t exist, so they’re not blocked by missing references.

  • Bypassing restrictions – Because the Flow directly inserts the asset record, it’s able to reference the expanded sn_ent_* classes without hitting the OOB asset creation checks that normally block them.

  • Controlled access – We scoped the catalog item to the right audience.


Outcome:

This approach gives Asset Managers a clean and guided way to create records using otherwise-unusable sn_ent classes in ITSM Pro, while maintaining data quality. If anyone else is stuck with sn_ent installed but without EAM, a tailored catalog item + Flow is a low-impact way to bridge the gap.