What this category's data looks like
In the graduate admissions re-examination and admission scenario, materials include the re-examination plan, candidate score sheets, adjustment lists, progress sheets, and statistical scope notes. The re-examination plan contains process nodes, scoring rules, dates, and signature fields; the candidate score sheet contains candidate IDs, subject scores, converted scores, and rankings; the adjustment list contains adjustment batches, source of preference, confirmation status, and receipts. Materials are updated by admissions batch: the plan is published before the re-examination, scores and progress are recorded daily during the re-examination, and the list and receipts are synchronized during the adjustment stage. When entering workflow orchestration, the re-examination plan serves as the branching basis and source of scope, the candidate score sheet and adjustment list serve as the verification drafts for records and statistics, and the progress sheet and statistical scope notes are generated by subsequent nodes continuing execution along the branches. Field characteristics center on candidate ID, name, date, quantity, signature, and receipt, and names and dates must be consistent across materials.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "progress sheet and statistical scope notes" are completed next by subsequent nodes continuing execution along the branches. When a node is triggered, the conversation enters an interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Re-examination plan | Fields, dates, and signatures: whether the process nodes, scoring rules, date fields, and signature fields in the plan are complete, and whether they are consistent with the batch dates in the score sheet and adjustment list | Check the options and branch connections one by one in the node, and confirm that the dates and signature fields in the plan serve as the branching basis; trigger once, view the node status in the run records, and reference variables and nodeId in subsequent nodes for a trial run |
| Candidate score sheet | Whether the candidate ID, name, quantity, and date of the same record match between the score sheet and the adjustment list, and whether the versions are synchronized | Use one week of records to verify the totals, and compare candidate IDs and names one by one; reference variables in subsequent nodes for a trial run, and check whether the branch direction and interaction status records are consistent with the scope of the score sheet |
| Adjustment list | Whether the names, quantities, dates, and receipts in the adjustment list are consistent with the score sheet and re-examination plan, and whether entries missing signatures or receipts are marked | Check the options and branch connections one by one in the node, and confirm that the confirmation status and receipts in the adjustment list serve as branching conditions; trigger once, and view the node status and the correspondence of nodeId in the run records |
| Progress sheet and statistical scope notes | Whether the record counts and statistical counts match, whether the scope is written in the header, and whether exceptions are clearly stated | Use one week of records to verify the totals, and check whether the scope and exceptions are clearly stated; reference variables in subsequent nodes for a trial run, and verify whether the branch direction and interaction status records are consistent with the scope in the progress sheet header |
Three common errors
- Symptom: the name, quantity, or date of the same candidate does not match between the score sheet and the adjustment list. Cause: the two materials are maintained separately, are not uniformly verified by candidate ID, and versions are not synchronized.
- Symptom: the re-examination plan date is inconsistent with the score sheet batch date, and the signature field or receipt is missing. Cause: the materials are updated at different paces, and after the plan is revised it is not synchronized to the score sheet and adjustment list.
- Symptom: after selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: the options and branch connections were not checked one by one, and the interaction status records were not confirmed in the run records.
How to verify the setup
This feature's acceptance: run trials for each option one by one, check the branch direction and interaction status in the run records, and confirm that variables, nodeId, and option branches correspond; trigger once to view the node status, and rule out taking the default branch after selecting an option, the process stopping after the interaction is completed, and repeatedly entering the interaction in the same session.
Business testing: use one week of records to verify the totals, check whether the scope and exceptions are clearly stated, whether the record counts and statistical counts match, and whether the scope is written in the header.
- Check the options and branch connections one by one in the node, trigger once to view the node status in the run records, and confirm that the interaction status is recorded.
- Reference
variablesandnodeIdin subsequent nodes for a trial run, check the branch direction and interaction status records, and use one week of records to verify the totals and scope exceptions.