Conditions for database view to collect deflection logs resolved by KBSummary<!-- /*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: ; } } After the user enters a search term, when the search result is displayed, a new deflection log is created. The initial state of the deflection log is "resolved"When no result is found in the search result, the state becomes “no_response”If negative feedback on the synthesized result page gets clicked, the state becomes “not resolved”If positive feedback on the synthesized page gets clicked, the state becomes “resolved” User reaction to KB / Catalog / Topic does not change the state of the deflection log.When the user enters a new search term, a new deflection log gets created.Mid topic search does not create deflection log handling.