What this category's data looks like
In the course selection, scheduling, and classroom resource dispatch scenario, materials fall into three categories: course offering plans, scheduling tables, and course selection rules. Fields include course name, class size, class date, classroom number, signature field, and receipt. When these materials enter the conversation record function, each plays an evidentiary role: the course offering plan provides the baseline for courses and class sizes, the scheduling table provides the correspondence between time and classrooms, and the course selection rules provide constraint conditions. The update cadence for material versions and change maintenance is to re-register after each round of scheduling adjustments, with old versions retained and traceable. The conversation record API, by application and session dimensions, outputs only the session message list and the total record count, including role and reference information; the version ledger and change records must be continued manually or by an external system.
Configuration and implementation checks
The conversation record API (by application and session dimensions) outputs only the session message list and the total record count, including role and reference information; the version ledger and change records must be continued manually or by an external system.
| Object | Check | Verification action |
|---|---|---|
| Course offering plan | Course name, class size, course start date, and signature field must correspond item by item with the scheduling table; the version number must be unique and old versions traceable | Use chatId to pull the corresponding session records, verify whether the course name and class size in the messages match the plan, and compare dataId to locate a single reference |
| Scheduling table | Class date, period, and classroom number must be consistent with the time constraints in the course selection rules; after changes, references must be updated synchronously | Paginate to retrieve all records, inspect the reference and duration fields of a single record via value, and confirm that the date and classroom number are not misaligned |
| Course selection rules | Course selection capacity, priority, and deadline must match the class size in the course offering plan; missing signature or receipt is considered not effective | Verify the total record count total and response code of 200, and check item by item whether the role field matches the original conversation between question and answer |
Three common errors
- Symptom: The name, class size, or date of the same course does not match across two materials. Cause: Versions are not synchronized, and the old scheduling table was not updated when the course offering plan changed.
- Symptom: The scheduling table has already adjusted the classroom, but the course selection rules still reference the old classroom number. Cause: The change record only modified one place, and the reference was not refreshed synchronously.
- Symptom: The course offering plan lacks a signature or receipt, yet the scheduling table has already been published. Cause: The registration step did not verify the signature field, and the version ledger lacks effective credentials.
How to verify the setup
Acceptance for this feature: Paginate to retrieve all records by the total record count total, sample one record to verify the role, reference information, and time, and confirm that the status code is 200 and the number of messages matches the total record count.
Business test: Change one piece of content and see whether the version number and references are updated synchronously
- Use
chatIdanddataIdto locate a single record, and verify whether the role field and reference information correspond to the actual session - Pull two pages consecutively and compare the offset and total record count to confirm there are no omissions and that the number of references is recorded separately by array length