How does ServiceNow handle a Configuration Item (CI) class change? I see that this is possible but I'm not sure what the logic and the rules are when this happens. For example, it seems that fields (including data) that exist in the previous class get dropped/deleted when the CI is changed to a new class that does not have those fields. Is there any way to intercept this process to add custom mappings?
Are there any other considerations I should keep in mind in changing a CI class?
Are there recommended best practices on how CI class changes should be handled? Or, is it generally a bad idea and should be avoided?
