What this category's data looks like
This page focuses on question acceptance and missing-item follow-up in technical college academic education management. The source materials are three types: student registration forms, teaching plans, and skills training records. Student registration forms are updated at semester registration milestones, with fields including student name, student ID, major, registration date, and signature; teaching plans are updated by major and grade version, with fields including course name, class hours, semester offered, and approval signature; skills training records are updated by training batch, with fields including training item, number of workstations, training date, and instructor signature. When the three types of materials enter the form input node, their roles differ: student registration forms provide identity and registration status, teaching plans provide the basis for courses and class hours, and skills training records provide the basis for the training process and results. After the form collects fields one by one, it passes them to subsequent nodes, where subsequent nodes or humans compare names, quantities, dates, and signatures to identify missing items and generate follow-up questions.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). "Acceptance records and items to be completed" are then handled by subsequent nodes or humans. After the form input node is triggered, the conversation enters an interactive state and the workflow state is recorded. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Student registration form | Fields include student name, student ID, major, registration date, and signature; the name, major name, and date must be consistent with those in the teaching plan | Check the field names one by one in the node configuration, use formInput to reference the fields and run a trial, and compare the names and dates in the two materials |
| Teaching plan | Fields include course name, class hours, semester offered, and approval signature; the item name, quantity, and date must be consistent with those in the skills training records | Check the required settings one by one, use userSelect in subsequent nodes to retrieve the course field value and run a trial, and check whether the version is synchronized |
| Skills training records | Fields include training item, number of workstations, training date, and instructor signature; if the signature or receipt is missing, a follow-up question is needed to complete it | Reference this field in subsequent nodes and run a trial, check whether the signature and receipt are complete, and generate a follow-up question when an item is missing |
| Field transfer after submission | Subsequent nodes can retrieve the corresponding field values; submission is not allowed when a required item is empty; the conversation does not remain in the interactive state | Reference the formInputResult field value in subsequent nodes and run a trial, and check that the retrieved value matches the filled-in value |
Three common errors
- Symptom: The name or major name of the same student does not match between the student registration form and the teaching plan. Cause: The two materials are entered separately, and no cross-check of names and dates is performed.
- Symptom: The teaching plan has already changed versions, but the skills training records are still reported according to the old version's course names and class hours. Cause: The versions are not synchronized, and the material update rhythms are inconsistent.
- Symptom: The skills training records lack the instructor signature or receipt, and the training results cannot be confirmed after acceptance. Cause: The signature and receipt are not listed as required, and no follow-up question is asked at submission.
How to verify the setup
Acceptance of this feature: fill out the form once and submit it, check whether the field values retrieved by subsequent nodes match the filled-in values, whether submission is not allowed when a required item is empty, and whether the conversation does not remain in its original state due to interaction.
Business test: submit a question that lacks key information and see whether it asks a follow-up question before answering, and whether the follow-up items correspond to the fields in the student registration form, teaching plan, and skills training records.
- Check the field names and required markers one by one in the node configuration to ensure that key material fields are marked as required.
- Reference the
formInputResultandselectResultfield values in subsequent nodes and run a trial, and check that the retrieved values match the filled-in values.