Understanding Change Model Queries and Type Field Behavior in ServiceNowIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The customer has queries regarding the 'Model' field in change requests and its relationship with the 'Type' field, specifically:1. Whether the 'Model' field can have values other than 'Standard', 'Normal', or 'Emergency'.2. Whether to hide the 'Model' choice for the 'Type' field using a client script until they start using models to create change requests.3. Whether a change request's 'Type' field defaults to 'Model' if not configured in the change model's 'Record Preset'. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Yokohama Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. Can the "Type" field be anything other than Standard, Normal, or Emergency? Yes. The Type field can display Model only when: The change request is created using a change model, andThe change model’s Record preset is set to use the type = model, andThe system property com.snc.change_management.change_model.type_compatibility is set to false (indicating workflows are type-based rather than model-based). In all other cases, the available types remain Standard, Normal, and Emergency. 2. Should the "Model" choice be hidden using a client script? No. If you do not want the Model option to appear in the Type field, the recommended approach is: Update the sys_choice table entry for the Type field and set inactive = true for the "Model" option. 3. What happens if a change model does not define a Type in its "Record preset"? At the change model level: If no Type is defined in the Record preset, the system automatically sets Type = Model for that change model.Recently, the platform default for this behavior was updated by engineering from Normal → Model at the time of change model creation. However, the default remains Normal in Yokohama releases.NOTE: Once change models are in use, workflows are determined by models, and the Type field becomes less relevant. At the change request level: If com.snc.change_management.change_model.type_compatibility is true, any change request created directly (e.g., from change_request.do or from a template with a default type) will have its type set to Normal by default.Even if a change model exists with Type unspecified, the change request defaults to Normal unless explicitly configured otherwise. Conclusion If the Type is not Standard or Emergency, it will default to Normal, unless models are in use with different presets. The Model choice can be disabled by setting its sys_choice entry to inactive, instead of using a client script. When using change models, the Type field’s role diminishes, since workflows are model-driven rather than type-driven.