Hi @Vivek Prakash ,
Model Category is closely tied to Asset Class and CI Class, which define how assets and configuration items (CIs) are categorized and managed across ITAM (IT Asset Management) and CMDB (Configuration Management Database). Once these fields are set, they generally aren't editable, because modifying them can have significant impacts on various parts of the system.
Here's what to consider if there's a requirement to edit Asset Class and CI Class on a Model Category:
Impact on Existing Data:
- Changing the Asset Class or CI Class on an existing Model Category could affect any records (assets or CIs) that are already associated with that category. For example, existing assets and CIs might no longer align with the new class or may not be handled correctly by existing processes.
Workflows & Business Rules:
- Many workflows, business rules, and UI policies are built around specific asset and CI classes. Changing the class could result in unintended behavior in workflows like procurement, change management, or incident management processes.
Reporting and Dashboards:
- Reports and dashboards may rely on specific classes for categorizing assets and CIs. Changing these could lead to inaccurate or incomplete reporting.
Integration with Other Modules:
- ITAM and CMDB often integrate with other modules like ITSM (Incident, Change, and Problem Management). Modifying the Asset Class or CI Class might disrupt these integrations.
If this resolves your issue, kindly mark it as Correct 
Best regards,
Moin
Hi @Vivek Prakash ,
Model Category is closely tied to Asset Class and CI Class, which define how assets and configuration items (CIs) are categorized and managed across ITAM (IT Asset Management) and CMDB (Configuration Management Database). Once these fields are set, they generally aren't editable, because modifying them can have significant impacts on various parts of the system.
Here's what to consider if there's a requirement to edit Asset Class and CI Class on a Model Category:
Impact on Existing Data:
- Changing the Asset Class or CI Class on an existing Model Category could affect any records (assets or CIs) that are already associated with that category. For example, existing assets and CIs might no longer align with the new class or may not be handled correctly by existing processes.
Workflows & Business Rules:
- Many workflows, business rules, and UI policies are built around specific asset and CI classes. Changing the class could result in unintended behavior in workflows like procurement, change management, or incident management processes.
Reporting and Dashboards:
- Reports and dashboards may rely on specific classes for categorizing assets and CIs. Changing these could lead to inaccurate or incomplete reporting.
Integration with Other Modules:
- ITAM and CMDB often integrate with other modules like ITSM (Incident, Change, and Problem Management). Modifying the Asset Class or CI Class might disrupt these integrations.
If this resolves your issue, kindly mark it as Correct
Best regards,
Moin
