What this category's data looks like
This page focuses on credit management for primary and secondary school teacher training. Materials come from training notices, credit recognition forms, and participant lists. The update cadence advances with training batches and recognition cycles, and the field characteristics center on name, ID number, subject, class hours, credits, training date, signature, and receipt. When entering the model access and configuration function, the training notice plays the role of initiation and basis, the credit recognition form plays the role of result and signature, and the participant list plays the role of personnel and quantity verification. In the server-side model channel configuration, these three types of materials first complete model binding, and are then handed over to dialogue and retrieval for use, to draft issuable material drafts and handover records. Only when fields are complete, responsible persons are clear, and versions and dates are consistent can they enter the next step of sign-off.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, outputting model binding relationships and channel responses. The issuable material drafts and handover records are then completed by subsequent AI nodes, code nodes, or manual work. Models are divided into five categories: language, index, rerank, speech synthesis, and speech recognition. Different steps bind different model types.
| Object | Check | Verification action |
|---|---|---|
| Training notice | Check the name, date, and signature against the credit recognition form and participant list | Check whether the training name, start and end dates, and number of participants in the notice are consistent with the list, whether signatures and receipts are complete, and check whether the model identifier is consistent with the name listed in the document |
| Credit recognition form | Check class hours, credits, and personnel names against the participant list | Check whether the names, class hours, and credits in the recognition form correspond one by one with the list, whether the version and date are synchronized, and whether missing signatures or receipts are blocked |
| Participant list | Check quantity and date against the training notice | Check whether the number of people in the list is consistent with the number in the notice, whether names and ID numbers are duplicated or missing, and check whether the channel and key are consistent with the connected service |
| Model binding relationship | Correspond to the step to be used | In the model configuration, check the type labels: bind the index model to the retrieval step and the rerank model to the rerank step, check the value sources of maxContext and maxTokens, and separately record the number of references |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the training notice and the credit recognition form. Cause: During drafting, the same version was not used for backfilling, and fields were not checked one by one before handover.
- Symptom: The participant list has been updated, but the credit recognition form still uses the old version, and signatures or receipts are missing. Cause: The version was not synchronized, and the handover record did not record the change time and responsible person.
- Symptom: Retrieval reports an index model-related error, or the answer style changes abruptly after switching models. Cause: The model type bound to the step does not correspond to the step to be used, and the model identifier is inconsistent with the model name returned by the channel.
How to verify the setup
This function's acceptance: run one dialogue and one retrieval, check whether the model identifier in the response is consistent with the name listed in the document, check the value source of toolChoice, and confirm that quoteMaxToken is only used as the reference content budget, with the number of references recorded separately.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- In the model configuration, check item by item whether the model type corresponds to the step to be used, check whether the channel and key are consistent with the connected service, and check the model identifier against the model name returned by the channel.
- After drafting, check the name, quantity, date, and signature field by field against the training notice, credit recognition form, and participant list, and after confirming that the version and date are consistent, hand it over to the next step for sign-off.