What this category's data looks like
This page focuses on filing materials for vocational college program offerings. The sources are program offering filing forms, talent demand justifications, and faculty and equipment lists submitted by academic affairs offices and departments. The update cadence is weekly aggregation and monthly verification. The filing form carries the program name, code, program length, and signature fields; the justification materials record industry research dates, job mappings, and conclusions; the faculty and equipment list specifies the number of teachers, title structure, training equipment units, and arrival dates. When these three types of materials enter this feature, their roles differ: the filing form serves as the primary record anchor, the justification materials support fields, and the faculty and equipment list is used for cross-checking quantities and dates. Field characteristics center on names, quantities, dates, signatures, and receipts. The same record often appears with different wording across materials and must be compared item by item in the weekly records.
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 inputs and returns in the call record). The "progress table and statistical scope description" is then completed by a subsequent AI node or manual verification.
| Object | Check | Verification action |
|---|---|---|
| Program offering filing form | Fields include program name, code, program length, and signature; dates must be consistent with the justification materials | Open the filing forms one by one, verify the name wording, quantity, dates, and signature fields, and mark records missing signatures or receipts |
| Talent demand justification | The justification date, job mapping, and conclusion fields must match the program name and quantity in the filing form | Check the justification conclusions and dates item by item against the filing form, check whether versions are synchronized, and record inconsistent entries |
| Faculty and equipment list | The number of teachers, title structure, equipment units, and arrival dates must be consistent with the filing form's scope | Verify the list totals in the weekly records, check whether quantities and dates match, and confirm that signatures or receipts are complete |
| Tool call node | The introduction, parameter descriptions, and whether each is required must correspond to the material fields; toolChoice and functionCall can serve as identifiers | Verify the diamond connectors and node status on the canvas, run a test query missing required fields, and see whether it asks a follow-up question first |
Three common errors
- Phenomenon: the same program name is written differently in the filing form and the justification materials. Cause: the two materials are filled out by different personnel, the naming scope is not unified, and the discrepancy is only discovered during weekly record verification.
- Phenomenon: the number of teachers or equipment units does not match between the two materials. Cause: the list versions are not synchronized, old data is still referenced, and the statistical totals deviate from the record counts.
- Phenomenon: the filing form lacks a signature or receipt, and the justification date is inconsistent with the filing date. Cause: the material circulation step leaves no trace, the signature field is blank, dates are filled in arbitrarily, and verification cannot trace them.
How to verify the setup
This feature's acceptance: run a test query missing required parameters, check the inputs and returns in the call record, confirm whether it asks a follow-up question or calls according to the introduction, and verify whether the toolChoice and functionCall identifiers appear.
Business test: use one week of records to verify the totals, see whether the scope and exceptions are clearly stated, confirm that the record counts match the statistical counts, and write the scope into the table header.
- Open the tool node introduction field, check whether the description can be understood when taken out on its own, and verify the parameter descriptions and whether each is required one by one.
- Verify the diamond connectors and node status on the canvas, confirm that the tool call node is connected to the target tool, and then run a query missing fields to observe the return.