Need clarification on result_type for Configuration Finding records in Wiz migrationIssue <!-- /*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: ; } } Customer is working on Wiz migration using KB2344715 and following Option 2 to migrate existing data from old Wiz-built integrations to the new Vulnerability Response Integration with Wiz.During validation of sn_vulc_result records, we found the below logic in the migration script:var type = tr.getValue('x_wiz_cc_result_type');var resultType = type == 'Wiz Issue' ? 'issue' : '';tr.setValue("result_type", resultType);Based on this logic, only records with x_wiz_cc_result_type = Wiz Issue are getting result_type = issue. For other records, including Configuration Finding records, result_type remains blank.User validated this in their instance and wanted to confirm whether this is expected OOB behavior ?- Old Configuration Finding records after migration are updated to the new integration instance, but result_type stays blank- New Configuration Finding records created by the new SN-built Wiz integration also have result_type blank- Old Wiz Issue records after migration are getting result_type = issue- If we customize this script and set a value in result_type for Configuration Finding records, will it impact product behavior or future Wiz integration processing? Since new SN-built Configuration Finding records are also coming with blank result_type, please confirm whether this field is expected to remain blank and should not be customised. 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: ; } } All 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. Is the result_type behavior expected OOB? Yes, this is confirmed as expected, intentional behavior: • Old Configuration Finding records after migration → result_type remains blank: Expected • New Configuration Finding records from the SN-built Wiz integration → result_type blank: Expected • Old Wiz Issue records after migration → result_type = 'issue': Expected 2. Should result_type be customised for Configuration Finding records? No — please do not customize the migration script or set a value in result_type for Configuration Finding records. This is an intentional product decision. In the SN-built Wiz integration, cloud misconfiguration findings (Configuration Findings) are kept with an empty result_type, consistent with how other scanners handle this field. Other types of misconfigurations in Wiz will have result_type populated as applicable. As part of a broader standardisation effort, this same approach is planned across other scanners as well — so empty result_type for cloud misconfigurations is the intended, forward-looking behavior.