What this category's data looks like
Course scheduling and course consumption materials at training institutions come from class schedules, course consumption records, course adjustment applications, and conversation logs, with an update cadence that rolls forward by class session and course hour milestones. Class schedule fields include course name, class, teacher, classroom, date, and time slot; course consumption records include student, number of course hours, consumption date, and signature; course adjustment applications include the original class session, target class session, application date, and approval receipt. When the materials enter the conversation logs and auditing feature, the class schedule and course consumption records serve as the business source documents, and the course adjustment applications serve as the change vouchers, each carrying its own verification role: the class schedule defines the scheduling baseline, the course consumption records define actual consumption, and the course adjustment applications define the basis for adjustments. The conversation record interface pulls the message list by application and session dimension, and is used to retain operation traces; it does not replace the business ledger.
Configuration and implementation checks
This part is executed by the conversation record interface (by application and session dimension), which outputs the session message list and the total record count, including role and reference information. The handover-ready deployment status and operation records are then completed by humans or external systems; the interface only provides session evidence and does not write to the business ledger.
| Object | Check | Verification action |
|---|---|---|
| Class schedule | Fields, dates, and signatures are complete, and each entry corresponds one by one with the course consumption records | Verify the course name, class, teacher, date, and time slot, and check the signature column and receipt |
| Course consumption record | The number of course hours and the consumption date match the class schedule, and signatures and receipts are not missing | Compare the student, number of course hours, and consumption date, and check whether the signature and receipt are complete |
| Course adjustment application | The names and dates of the original class session and target class session match, and the approval receipt is complete | Verify the original class session, target class session, application date, and approval receipt |
| Conversation log | The total record count matches the number of paginated entries, and role and reference information can be queried | Page through by chatId to retrieve everything, verify dataId and value, and confirm the total and response code of 200 |
Three common errors
- Symptom: The same course consumption record has mismatched name, quantity, and date between the class schedule and the course consumption form. Cause: The two materials are registered separately and are not backfilled and verified against the same class session number.
- Symptom: A course adjustment application has already been approved, but the class schedule and course consumption records still follow the original class session. Cause: The version was not synchronized, and the change voucher was not written back to the scheduling and course consumption source documents.
- Symptom: A course consumption record lacks a signature or receipt, and that item is blank on the handover form. Cause: The operation record did not flow with the class session, and the human or external system did not complete registration and review.
How to verify the setup
Feature acceptance: Page through by the total record count to retrieve everything, sample one entry to verify the role, reference information, and time; confirm the total and response code of 200, and check whether _id, dataId and value can be queried.
Business test: Check item by item against the handover form once to see which record is missing; compare the name, quantity, date, and signature of the class schedule, course consumption records, and course adjustment applications one by one.
- Page through by
chatId, pull two consecutive pages and compare the offset and total record count to confirm there are no omissions. - Open one record to verify the role, reference information, and elapsed time fields, and check whether
dataIdandvalueare complete.