What this category's data looks like
Graduate admissions re-examination and admission materials center on the re-examination plan, candidate score sheets, and transfer lists, updated by admission year and batch. Fields include candidate number, name, preliminary exam total score, re-examination score, total score, ranking, proposed admission status, transfer source, date, and signature column. The re-examination plan determines weights and procedures, the score sheet carries scores and rankings, and the transfer list records sources and destinations. When these three types of materials enter workflow orchestration, the re-examination plan serves as the basis for judgment and the source of node branch conditions, the score sheet serves as the benchmark for anomaly comparison, and the transfer list serves as the entry point for cross-table traceback, jointly supporting the generation and circulation of anomaly lists and review conclusions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option. The "Anomaly List and Review Conclusion" is completed by subsequent nodes continuing execution along the branch.
| Object | Check | Verification action |
|---|---|---|
| Re-examination plan | Whether the weights, dates, and signature columns in the plan are consistent with the score sheet and transfer list | Check fields, dates, and signatures item by item; verify options and branch connections one by one in the node; record discrepancies |
| Candidate score sheet | Whether the name, quantity, and date of the same candidate match between the score sheet and the transfer list | Reference variables and nodeId, run a trial in a subsequent node, and confirm that the selection result variable has been passed |
| Transfer list | Whether the list version is synchronized and whether receipts or signatures are complete | Trigger a user selection node once, check the node status in the run record, and confirm the branch direction |
| Anomaly record | Whether the anomaly is supported by original records and whether the reviewer has signed | Trace back from the anomaly list to the source materials, and check names, quantities, dates, and signature receipts |
Three common errors
- Phenomenon: The name, quantity, and date of the same candidate do not match between the score sheet and the transfer list. Cause: The two materials are maintained separately, without cross-table comparison and version synchronization.
- Phenomenon: After the re-examination plan is updated, the score sheet and transfer list still use the old weights and dates. Cause: Versions are not synchronized, and node branches still follow old conditions.
- Phenomenon: The transfer list lacks signatures or receipts, and anomaly records cannot be traced to the source. Cause: The material circulation process leaves no trace, and the reviewer has not signed for confirmation.
How to verify the setup
Acceptance of this function: Run trials option by option, check the branch directions and interaction states in the run records, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business test: Create an anomaly record, see whether it can be traced to the source materials, and check the fields, dates, and signatures of the re-examination plan, candidate score sheet, and transfer list.
- Check options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger a user selection node once, and check the node status and branch direction in the run record.