What this category's data looks like
In the course selection, scheduling, and classroom resource allocation scenario, the materials entering the progress record and statistical verification stage are mainly of three types: course offering plans, scheduling tables, and course selection rules. Course offering plans are usually issued by semester or teaching week, and contain the course name, course code, offering unit, planned enrollment, start and end dates, and a signature field for the person in charge; scheduling tables are updated weekly or daily, and contain the course, teacher, classroom, time slot, week number, and adjustment notes; course selection rules record the selection batch, capacity limit, prerequisite conditions, screening priority, and effective date. The three types of materials play different roles in the function: the course offering plan is the upstream basis for the progress table, the scheduling table is the direct source of classroom resource occupancy, and the course selection rules determine which records are counted in the totals in the statistical criteria and which are listed separately as exceptions. The materials mostly enter as tables or structured text, the update rhythm is synchronized with the academic affairs week, and field names often have abbreviations and full names coexisting across different colleges.
Configuration and implementation checks
This step is executed by the tool call node in the workflow (the model decides whether to call it, and the node executes it), outputting the tool call result (the input parameters and return in the call record). The "progress table and statistical criteria description" is then completed by a subsequent AI node or manual verification. The tool description, parameter description, and whether it is required together determine whether to call it this time, and the call record retains the input parameters and return for verification.
| Object | Check | Verification action |
|---|---|---|
| Course offering plan | Whether the course name, course code, planned enrollment, start and end dates, and signature field correspond item by item with the scheduling table | Compare the name, quantity, and dates of the same course in the two materials, and separately mark entries missing a signature or receipt |
| Scheduling table | Whether the classroom, time slot, week number, and adjustment notes are consistent with the capacity and effective date in the course selection rules | Verify classroom occupancy and selection batches by week; for versions not yet synchronized, the version with a signed receipt prevails |
| Course selection rules | Whether the selection batch, capacity limit, prerequisite conditions, and screening priority are written into the header of the statistical criteria table | Write the situations counted in the totals and those treated as exceptions into the header, and verify the rule fields and dates item by item |
| Tool call node | Whether the tool description, parameter description, and whether it is required correspond to the business material fields | On the canvas, verify the diamond-shaped interface connections and node status, and test-run with a question missing a required parameter to see whether it asks a follow-up or calls directly |
Three common errors
- Symptom: the name, quantity, and dates of the same course do not match between the course offering plan and the scheduling table. Cause: the two materials are maintained separately, lacking a comparison step based on the signed receipt.
- Symptom: the scheduling table has been adjusted, but the course selection rules still count according to the old capacity. Cause: the versions are not synchronized, the update rhythm is misaligned with the academic affairs week, and the old version is not marked as invalid.
- Symptom: the totals in the progress table do not match the exception entries in the statistical criteria description. Cause: the criteria are not written into the header, the boundary between inclusion and exclusion relies on verbal agreement, and there is no signed confirmation.
How to verify the setup
Acceptance of this function: test-run with a question missing a required parameter, check the input parameters and return in the call record, and confirm whether it asks a follow-up or calls according to the description; at the same time, verify the three items of tool description, parameter description, and whether it is required, and check whether the values and returns of toolChoice and functionCall in the call record are consistent with the material fields.
Business test: use one week of records to verify the totals, see whether the criteria and exceptions are clearly written, and whether the names, quantities, and dates of the course offering plan, scheduling table, and course selection rules correspond item by item.
- Open the parameter configuration one by one, verify the description and whether it is required, and confirm that they correspond to fields that actually exist in the business materials.
- On the canvas, verify the diamond-shaped connections and node status, check whether the tool call node is connected to the target tool, and retain the input parameters and return in the call record.