What this category's data looks like
In the continuing education credit recognition scenario, three types of materials—course filing forms, study certificates, and credit recognition forms—enter the verification process in sequence. Course filing forms come from course-provider filing, are updated by semester batch, and their fields include course name, course number, filing date, and responsible person's signature; study certificates are submitted by learners, are updated on a rolling basis along with learning progress, and their fields include learner, course name, credit hours, completion date, and institution receipt; credit recognition forms are generated by the recognition handling step, are summarized by batch, and their fields include recognizer, course name, recognized credit hours, recognition date, and review signature. After these three types of materials enter this feature, the course filing form serves as the baseline reference, the study certificate serves as the object to be verified, and the credit recognition form serves as the result carrier, with field discrepancies between materials being located item by item through node orchestration.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "discrepancy list" is then completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| Course filing form | The four items—course name, course number, filing date, and responsible person's signature—must be consistent with the ledger | In the node, check the options and branch connections one by one, reference variables to read the filing fields and compare them with the ledger |
| Study certificate | The five items—learner, course name, credit hours, completion date, and institution receipt—must correspond to the filing form | In subsequent nodes, reference the selection result variable and run a trial once, using nodeId to locate the branch where the record is located |
| Credit recognition form | The five items—recognizer, course name, recognized credit hours, recognition date, and review signature—must be consistent with the study certificate | Trigger a user selection once, check the node status in the run record, and verify the recognition fields against the receipt fields |
| User selection node | Each option corresponds to one branch, and options and branch connections must correspond one-to-one | In the node, check the options and branch connections one by one, and confirm that the selection result variable has been passed to subsequent nodes |
Three common errors
- Symptom: For the same record, the course name and credit hours in the course filing form and the study certificate do not match. Cause: The versions of the two materials were not synchronized; the study certificate was submitted under the old course number, and the fields were not updated along with the filing.
- Symptom: The recognition date in the credit recognition form is inconsistent with the completion date in the study certificate. Cause: When the recognition form was summarized by batch, it carried over the date from the previous batch and did not write back the actual completion date of the current batch.
- Symptom: The study certificate lacks the institution receipt, and the credit recognition form lacks the review signature. Cause: The material submission step did not validate the signature and receipt fields, and records with missing items entered the verification process directly.
How to verify the setup
Feature acceptance: run a trial for each option, check the branch direction and interaction state in the run record, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business testing: use one real record to find fields inconsistent with the ledger, record the discrepancy locations for course name, credit hours, and date, and hand them to the reviewer for confirmation and write-back.
- In the node, check the options and branch connections one by one, confirm that each option corresponds to one branch, and use
variablesto reference the selection result variable. - Trigger a user selection once, check the node status in the run record, use
nodeIdto locate the branch where the record is located, and verify the course name, credit hours, date, and signature fields.