What this category's data looks like
This page addresses the corporate compliance and security training category. Materials include compliance training courseware, security operating procedures, exam records, draft materials that can be issued, and handover records. Sources are training system documents, regulatory clauses, position operation cards, historical exam ledgers, and signed receipts. The update cadence rolls with system revisions, regulatory changes, position adjustments, and training batches. Field characteristics center on name, quantity, date, version, responsible person, and signature field. When materials enter knowledge base retrieval, courseware and procedures serve as candidate snippet sources, while exam records and handover records serve as the basis for field verification; retrieval results only provide candidate snippets and similarity scores for subsequent nodes or manual drafting and signing, and do not directly produce statistical tables or authorization results.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate snippets and similarity scores (after pattern, merge, rerank, filter, and limit trimming). Draft materials that can be issued and handover records are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | Name, version, date, and signature field are complete and consistent with exam records | In the search test, switch searchMode between semantic, full-text, or hybrid, compare candidate snippets and scores, and verify whether the courseware version and date are synchronized |
| Security operating procedures | Name, quantity, date, and responsible person are clear; missing signature or receipt is blocked | Test once each with synonymous questions, see whether candidates include both semantic and full-text results, then verify whether key snippets are retained after similarity filtering |
| Exam records | Identified when the name, quantity, and date of the same record do not match across two materials | Compare the order of the top few items before and after enabling usingReRank, record the number of candidates and scores, and check whether the cited text covers key fields |
| Draft materials that can be issued and handover records | Fields are complete, responsible person is clear, version and date are consistent, and it can be handed to the next step for signing | Draft according to the template and complete one handover, verify the number of cited items after limit trimming, and missing items are blocked by subsequent nodes or manually |
Three common errors
- Phenomenon: The name and quantity of the same exam record do not match between the courseware and the handover record. Cause: Candidate snippets come from different versions and were not checked in sync by date and version.
- Phenomenon: A handover record lacks a signature or receipt but is still treated as issuable material. Cause: Field validation only looks at candidate content and does not list the signature field and receipt as required items.
- Phenomenon: The same question phrased differently fails to recall the key passage. Cause: The retrieval mode does not match the material form, and order changes before and after reranking are not recorded.
How to verify the setup
Feature acceptance: Test once each with synonym-rewritten questions, compare candidates and scores, then toggle reranking to observe the order of the top few items; record the number of candidates and scores, and verify the effects of similarity, limit, searchMode, and usingReRank.
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the knowledge base search test, switch retrieval modes, compare candidate snippets and scores, and confirm that semantic and full-text results have both been merged.
- Draft a material draft according to the template and complete one handover, checking item by item the name, quantity, date, version, responsible person, and signature receipt.