What this category's data looks like
In the grade entry and credit recognition scenario, materials are mainly of three types: transcripts, deferred examination applications, and makeup examination arrangements. Transcripts come from course records after entry by the course instructor; deferred examination applications are submitted by students and formed after approval; makeup examination arrangements are generated by academic affairs based on the deferred examination and failed-course lists. The three types of materials update at different rhythms: transcripts change with entry and corrections; deferred examination applications advance with approval nodes; makeup examination arrangements adjust with confirmation of venue and time. When materials enter workflow orchestration, each plays a different role: transcripts provide the course name, credits, grade, and entry date; deferred examination applications provide the course, reason, approval signature, and receipt; makeup examination arrangements provide the makeup examination course, time, location, and responsible person. Field characteristics are concentrated in course name, credit count, date, signature, and version number. During handover, it is necessary to ensure that the same record is consistent across the three materials.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The material drafts that can be issued and the handover records are completed by subsequent nodes continuing execution according to the branches. When a node is triggered, the conversation enters an interaction state and records the workflow state. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Transcript | Fields complete: course name, credits, grade, entry date, and signature; date and version consistent | In the node, check the options and branch connections one by one, confirm that the transcript fields enter the corresponding branch; reference the selection result variable in subsequent nodes and run a trial once |
| Deferred examination application | Fields complete: course, reason, approval signature, and receipt; the same record's name, quantity, and date match the transcript | Trigger an interaction once, view the node status in the run record; check whether the course name, credit count, and date of the deferred examination application and transcript are consistent |
| Makeup examination arrangement | Fields complete: makeup examination course, time, location, and responsible person; version and date synchronized and no missing signature or receipt | Check the course name, quantity, and date of the makeup examination arrangement against the deferred examination application and transcript; check whether the version number and signature receipt are synchronized |
| Handover record | Responsible person clear, version and date consistent, missing items blocked | Draft one according to the template and complete one handover, check the branch direction and interaction state record |
Three common errors
- Phenomenon: The name, credit count, or date of the same course do not match between the transcript and the deferred examination application. Cause: The two materials were drafted separately, and field comparison and version synchronization were not performed before handover.
- Phenomenon: The makeup examination arrangement has been updated, but the transcript and deferred examination application still reference the old version. Cause: The version number was not synchronized with material changes, and the handover record did not indicate the effective date.
- Phenomenon: The deferred examination application or makeup examination arrangement lacks an approval signature or receipt, but the process still continues. Cause: The handover step did not list signature and receipt as release conditions, and missing items were not blocked.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and check whether the references of variables and nodeId are correct.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the node, check the options and branch connections one by one, and after triggering an interaction once, view the node status in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once, and check the passing result of
variablesandnodeId.