Chassis type is not populated with the "Windows OS - Desktops" and "Windows OS - Servers" discovery patterns when Win32_SystemEnclosure ChassisTypes returns 35DescriptionThe Pattern Designer "Windows OS - Desktops" and "Windows OS - Servers" discovery patterns leave chassis_type blank on the resulting CI when the WMI class Win32_SystemEnclosure returns ChassisTypes=35 (Mini PC). The OOB chassis_type lookup arrays only cover ChassisTypes values 1–27 (Desktops) and 1–24 (Servers), so value 35 falls through and is written as an empty strSteps to Reproduce Run a Windows discovery on the desktop/serverand see the step insert chassis_type to cmdb_ci_computer doesnt update value 35Investigation Summary:the chassis type value is collected during discovery, but the value is not populated on the CI record. This appears to be happening for all affected CIs.Discovery log snippet:5 Transform value for chassis type2026-04-26 19:30:46: setAttribute(Win32_SystemEnclosure,[{ChassisTypes=35, internal_classname=Win32_SystemEnclosure, OBJECT_REFERENCE=null, SerialNumber=8CG8180PXT, internal_namespace=root/cimv2, __CLASS=Win32_SystemEnclosure, Tag=System Enclosure 0, row_number=1}])2026-04-26 19:30:46: Execution time: 0 ms6 Insert chassis_type to cmdb_ci_computer2026-04-26 19:30:46: setAttribute(cmdb_ci_computer,[{chassis_type=}])2026-04-26 19:30:46: Execution time: 0 msFrom the logs, the WMI data is returning ChassisTypes=35, but during the next pattern step, the value is getting transformed to blank and inserted as:chassis_type=We checked the OOB eval script used for chassis type transformation, and value 35 does not appear to be configured/mapped there.WorkaroundworkaroundRelated Problem: PRB2022107