What this category's data looks like
The data for this category mainly consists of three types: course filing forms, study certificates, and credit hour recognition forms. Course filing forms come from the course-offering unit and record the course name, number, credit hours, start date, and signature of the person in charge; study certificates come from the learning platform or in-person attendance sign-in and record the learner's name, course name, credit hours, completion date, and signature of the issuer; credit hour recognition forms are compiled by the recognition agency and record the recognition conclusion, recognition date, and signature of the handler. The three types of materials update at different rhythms: filing forms change as courses are offered, study certificates are generated as learning is completed, and recognition forms circulate as batches are recognized. When entering the multi-turn dialogue and prompts feature, filing forms provide the course baseline fields, study certificates provide the completion facts, and recognition forms provide the recognition conclusion and responsibility allocation. The names, quantities, and dates of the three must be consistent, versions and signature receipts must be synchronized, and missing items must be blocked during drafting and handover.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in the application settings, and the output references the historical message range and answer constraints. "Signable material drafts and handover records" are then completed by the model. Memory turns control how many previous dialogue turns can be referenced at most when answering; too small a value fails to use prior context, while too large a value brings in irrelevant content and increases consumption.
| Object | Check | Verification action |
|---|---|---|
| Course filing form | Fields, dates, and signatures are complete, and the course name and number can be verified | Check the memory turns value in the application settings, and check whether the course name, number, credit hours, start date, and signature of the person in charge are complete |
| Study certificate | Fields, dates, and signatures are complete, and the course name and credit hours match the filing form | Run a trial with two consecutive questions, and in the second round ask about the study certificate fields for the same course to see whether it carries over the reference from the first round |
| Credit hour recognition form | Fields, dates, and signatures are complete, and the recognition conclusion and responsibility allocation are clear | Compare the usage records of two runs, and check whether the recognition form version and date are synchronized and whether the handler's signature and receipt are complete |
Three common errors
- Phenomenon: The course name and credit hours of the same record do not match between the course filing form and the study certificate. Cause: During drafting, the baseline fields of the filing form were not used as the standard, and the two materials were filled in separately.
- Phenomenon: The version of the credit hour recognition form was not synchronized, and the old recognition conclusion continued to be referenced. Cause: The handover record did not indicate the version and date, and the next stage did not sign off according to the latest version.
- Phenomenon: The study certificate lacks the issuer's signature or the handover receipt is missing. Cause: Missing-item blocking was not set up during drafting and handover, and field completeness was not checked before issuance.
How to verify the setup
Acceptance of this feature: ask two consecutive follow-up questions and see whether the second question carries over the reference from the first; check the memory turns value in the application settings, and use chatId, messages, and variables to record the historical message range and answer constraints.
Business test: draft one according to the template and complete one handover to see whether missing items are blocked.
- Check the memory turns value in the application settings and confirm that it matches the prior context range required by the question.
- Run a trial with two consecutive questions and check the reference carryover in the second round and the
messageshistorical range.