What this category's data looks like
This page addresses the scheduling and lesson consumption scenarios of training institutions. The core materials include three types: class schedules, lesson consumption records, and schedule change requests. Class schedules are updated weekly or monthly, with fields including course name, class, teacher, classroom, start and end times, week number, and signature column; lesson consumption records are generated per session, with fields including student, course, number of lesson hours, teaching date, teacher confirmation, and parent receipt; schedule change requests are initiated as needed, with fields including original session, target session, reason for change, applicant, approver, version number, and date. When these materials enter the multi-turn dialogue and prompt feature, the class schedule serves as the scheduling baseline, the lesson consumption record serves as the consumption evidence, and the schedule change request serves as the basis for change; based on these, the model drafts issuable material drafts and handover records. Once the fields are complete, responsible parties are clear, and the version and date are consistent, they are handed over to the next stage for sign-off.
Configuration and implementation checks
This step is executed by the memory turns and prompt configuration in the application settings, outputting the reference historical message range and answer constraints. The issuable material drafts and handover records are then completed by the model. The memory turns control how many previous rounds of dialogue can be referenced at most when answering. If the value is too small, the preceding text cannot be used; if the value is too large, irrelevant content is brought in and consumption increases.
| Object | Check | Verification action |
|---|---|---|
| Class schedule | Whether the course name, class, teacher, classroom, start and end times, week number, and signature column are complete, and whether the date and version are consistent | Check the current memory turns value in the application settings, run a trial with two consecutive rounds of questions, and check whether the second round can correctly carry forward the first round's reference to the class schedule fields |
| Lesson consumption record | Whether the student, course, number of lesson hours, teaching date, teacher confirmation, and parent receipt are complete, and whether the name, quantity, and date of the same record match between the class schedule and the lesson consumption record | Put the class schedule and lesson consumption record into the same conversation, use messages to observe the historical message range, and confirm that the fields and version referenced by the model are consistent |
| Schedule change request | Whether the original session, target session, reason for change, applicant, approver, version number, and date are complete, and whether missing signatures or receipts are blocked | Use chatId to distinguish different handover sessions, use variables to carry the version number and date, and complete one handover to see whether missing items are blocked |
| Handover record | Whether the responsible party, sign-off time, version, and date are consistent, and whether the receipt is complete | Compare the usage records of two runs to confirm that the run consumption changes accordingly after adjusting the turns, and that the handover record does not mix in irrelevant historical messages |
Three common errors
- Symptom: The course name, number of lesson hours, and teaching date of the same lesson consumption record do not match between the class schedule and the handover record. Cause: The two materials were drafted separately, and the field sources were not checked against a unified standard.
- Symptom: The schedule change request has been updated, but the class schedule and lesson consumption record still reference the old version, and the version and date are inconsistent. Cause: The version was not synchronized, and the historical message range brought in old content.
- Symptom: The handover record lacks teacher confirmation or parent receipt, and the next stage cannot sign off. Cause: During drafting, the signature column and receipt column were not checked item by item according to the template.
How to verify the setup
Acceptance of this feature: Ask two consecutive follow-up questions and see whether the second question carries forward the reference of the first question; use messages to observe the referenced historical message range and confirm that the answer constraints take effect.
Business test: Draft one copy according to the template and complete one handover to see whether missing items are blocked.
- Check the current memory turns value in the application settings and match it with the preceding text range required by the question.
- Use
chatIdandvariablesto mark the handover session and version fields, and compare the usage records of two runs.