What this category's data looks like
This page addresses the scheduling and class-cancellation scenarios of training institutions. The material comes from three types of academic administration ledgers: class schedules, class-cancellation records, and schedule-change applications. The update rhythm changes entry by entry with scheduling adjustments, class-cancellation confirmations, and schedule-change approvals. Class schedules record the course name, class date, time slot, instructor, and class; class-cancellation records record the student, course name, cancellation quantity, cancellation date, and signature; schedule-change applications record the original course, proposed new date, reason for the change, and approval signature. When these three types of material enter the multi-turn dialogue and prompt feature, each plays a different role: class schedules provide the time and course scope, class-cancellation records provide the quantity and signature evidence, and schedule-change applications provide the date change and approval receipt. Field characteristics center on four items: name, quantity, date, and signature. It is necessary to ensure that the same record is consistent across different materials, that versions are synchronized, and that signatures or receipts are complete.
Configuration and implementation checks
| Object | Check | Verification action |
|---|---|---|
| Object | Judgment | Verification Action |
| Class schedule | Whether the course name, class date, and instructor are consistent with the class cancellation record, and whether the signature column is complete | Check the memory turns value in the app settings, run a test with two consecutive follow-up questions, and check whether the second round inherits the references from the first round |
| Class consumption records | Whether the class consumption quantity, class consumption date, and student name correspond item by item with the class schedule and class adjustment application, and whether the receipts are complete | Compare the usage records from two runs, confirm the consumption changes after the round count adjustment, and verify the tokens of the quoted text in messages |
| Course adjustment application | Whether the original course, proposed adjustment date, and approval signature are synchronized with the timetable version, and whether any signature or receipt is missing | Access once with a restricted identity to check whether the visible scope corresponding to chatId and variables matches the settings |
Three common errors
- Symptom: The course name, quantity, and date of the same class-cancellation record do not match between the class schedule and the class-cancellation ledger. Cause: The two materials were entered separately, without item-by-item comparison and version synchronization.
- Symptom: The schedule-change application has been approved, but the class schedule still shows the original date, and the class schedule seen by parents is inconsistent with the class-cancellation record. Cause: The version was not synchronized, and the change was not written back to the externally visible materials.
- Symptom: The class-cancellation record lacks a signature or receipt, the schedule-change application lacks an approval signature, and the external entry point is still viewable. Cause: Signatures and receipts were not included in the visible-scope determination, and the authorization scope was not tightened with the material status.
How to verify the setup
Acceptance of this feature: ask two consecutive follow-up questions and see whether the second question inherits the references from the first question; at the same time, check whether the memory turn count value matches the reference scope of messages.
Business test: access once with a restricted identity, see whether the visible scope matches the settings, and ensure unauthorized content is not visible.
- Check the current memory turn count value in the application settings, run a trial with two consecutive questions, and confirm that the second round correctly inherits the references from the first round.
- Compare the usage records of two runs, check the consumption change after adjusting the turn count; check the visible scope corresponding to
chatIdandvariables.