What this category's data looks like
Graduate training process management centers on three core materials: the training plan, the proposal report, and the mid-term assessment form. The training plan records course credits and the arrangement of training stages; the proposal report records the topic selection, supervisor's comments, and proposal date; the mid-term assessment form records staged results, assessment conclusions, and signatures. When these three types of materials enter the question acceptance and missing-item follow-up feature, they play different roles: the training plan is used to compare whether courses and stages are complete, the proposal report is used to check the topic selection and dates, and the mid-term assessment form is used to confirm assessment conclusions and signatures. Materials are submitted in batches as the semester progresses, and the update rhythm is synchronized with the nodes of the training stages. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures. Within the same record, names, quantities, or dates may fail to match across different materials, versions may not be synchronized, or signatures and receipts may be missing.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "accepted records and items to be completed" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest.
| Object | Check | Verification action |
|---|---|---|
| Training plan | Whether course names, credit quantities, and training stage dates are consistent with the proposal report and mid-term assessment form | In the request preview, check the rendered address and request body fields, and use a sample request to compare the response, confirming that names and quantities match |
| Proposal report | Whether the topic selection name, proposal date, and supervisor signature are complete, and whether they are synchronized with the version of the mid-term assessment form | Check the request header Authorization and the variable sources, and inspect whether the date and signature fields in the returned fields are empty |
| Mid-term assessment form | Whether the assessment conclusion, assessment date, and signature receipt are complete, and whether they are synchronized with the version of the training plan | In the variables panel, check the source of each placeholder, and confirm that variables and responseData can be traced to specific sources |
| HTTP interface and external system | Whether the request address, path parameters, and request body fields are consistent with the external interface agreement | In the request preview, view the complete rendered address, and use a sample request to compare the returned fields and status code |
Three common errors
- Symptom: the same course name fails to match between the training plan and the mid-term assessment form. Cause: the two materials are submitted separately, the names are not filled in according to the same standard, and the versions are not synchronized.
- Symptom: the proposal date and the mid-term assessment date fail to match in quantity or date within the same record. Cause: materials are entered in batches, date fields are not backfilled, and signatures or receipts are missing.
- Symptom: the request returns 401 or the external system receives empty fields. Cause: the source of the
Authorizationvalue is incorrect, or the placeholder variables are not parsed into actual values.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample, confirming that variables and responseData can be traced to specific sources.
Business test: submit a question that lacks key information, and see whether it asks a follow-up question before answering.
- In the request preview, check the complete rendered address, request header names, and value sources, confirming that
Authorizationis passed in according to the external system's requirements. - In the variables panel, check the source of each placeholder, and use a sample request to compare the returned fields, confirming that
variablesandresponseDataare consistent with the external interface agreement.