Understanding change type values in Upgrade History logs for prioritizing skipsSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The change type field in Upgrade History logs captures code changes in skipped records, including Script, HTML, and XML field value changes. Understanding change type values helps you prioritize which skips to review first, as skips with code changes require more attention than non-code element changes. Changes are tracked by comparing the new base system version against your current base version. This tracking indicates when the new base version contains changes (fixes or enhancements), signaling that you should review changes to customized files and decide whether to accept, merge, or keep your customized version.