Change model and Type field behavior in change requestsIssue <!-- /*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: ; } } This article addresses three common questions about how the Type field and change models interact in change requests: Can the Type field display Model as a choice option in addition to Standard, Normal, and Emergency?Should the Model choice in the Type field be hidden using a client script?What is the default Type value when a change model's Record Preset does not define a Type? 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 display Model as a choice option? Yes. The Type field can display Model only when all of the following conditions are met: The change request is created using a change model.The change model's Record Preset sets the Type field to Model.The com.snc.change_management.change_model.type_compatibility system property is set to false, indicating workflows are type-based rather than model-based. In all other cases, the available Type values are Standard, Normal, and Emergency. 2. Should the Model choice be hidden using a client script? No. To prevent the Model option from appearing in the Type field, update the Choice [sys_choice] table entry for the Type field and set Inactive to true for the Model option. 3: What is the default Type when no Type is defined in the Record Preset? At the change model level: If no Type is defined in the Record Preset, the system sets Type to Model for that change model. The platform default for this behavior was updated from Normal to 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 set to true, any change request created directly (for example, from change_request.do or from a template with a default type) defaults to a Type of Normal. Even if a change model exists with an unspecified Type, the change request defaults to Normal unless explicitly configured otherwise. Summary If the Type is not Standard or Emergency, it defaults to Normal, unless change models with different presets are in use.The Model choice can be disabled by setting its Choice [sys_choice] entry to Inactive, rather than using a client script.When using change models, the Type field's role diminishes because workflows are model-driven rather than type-driven.