What this category's data looks like
The materials for continuing education credit recognition usually include three types: course filing forms, study certificates, and credit recognition forms. The sources are training institutions, employers, and competent authorities, and the update cadence advances with training batches and the annual recognition cycle. Course filing forms carry the course name, number of credit hours, course start date, and institutional seal; study certificates carry the learner's identity, completion status, and receipt; credit recognition forms carry the recognition conclusion, recognition date, and review signature. When entering workflow orchestration, the three types of materials play different roles: the filing form provides the course and credit-hour baseline, the study certificate provides the fact of completion, and the recognition form provides the conclusion and signature basis. Field characteristics are concentrated in four places: name, quantity, date, and signature, and the same record must remain cross-referenceable across multiple materials. Material versions and change maintenance require that the current version be unique, old versions be traceable, and references be synchronized; changing one piece of content requires checking whether the version number and references in all places are updated in sync.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. The "version ledger and change records" are continued and completed by subsequent nodes according to the branch. When a 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.
| Object | Check | Verification action |
|---|---|---|
| Course filing form | Fields, dates, and signatures: whether the course name, number of credit hours, course start date, and institutional seal are complete and consistent with the study certificate | Check the options and branch connections one by one in the node, confirm the branch direction corresponding to the filing form, and reference variables in a subsequent node for a trial run |
| Study certificate | Fields, dates, and signatures: whether the learner's identity, completion status, receipt date, and seal match the filing form and recognition form | Trigger a user selection node once, view the node status and nodeId in the run record, and confirm that the study certificate branch was correctly selected |
| Credit recognition form | Fields, dates, and signatures: whether the recognition conclusion, recognition date, and review signature are consistent with the completion status in the study certificate | Reference the selection result variable variables in a subsequent node and perform a trial run, checking that the recognition form branch did not go to the default branch |
| Version ledger | Current version unique, old versions traceable, references synchronized: after changing one piece of content, whether the version number and references are updated in sync | After changing one piece of content, rerun and check the branch direction and interaction status records in the run record to confirm that references are synchronized |
Three common errors
- Symptom: The name, number of credit hours, and date of the same record do not match between the course filing form and the study certificate. Cause: The materials are maintained separately, the field definitions are not unified, and after changes the other material is not backfilled.
- Symptom: The credit recognition form has been updated, but the knowledge base or external documents still reference the old version. Cause: The version was not synchronized, the old version was not marked invalid, and references were not updated with the version number.
- Symptom: The study certificate lacks a signature or receipt, but the credit recognition form has already given a recognition conclusion. Cause: The signature and receipt steps were not included in branch verification and were skipped during material flow.
How to verify the setup
Acceptance for this feature: run trials option by option, check the branch direction and interaction status in the run record, and confirm that each option corresponds to one branch, the selection result variable has been passed to subsequent nodes, and the process continues downward after the interaction is completed.
Business test: change one piece of content, see whether the version number and references are updated in sync, and check whether the fields, dates, and signatures of the course filing form, study certificate, and credit recognition form still match.
- In the user selection node, check the options and branch connections one by one, confirm that no option falls to the default branch, and record the branch direction corresponding to
nodeId. - Trigger an interaction once, view the node status and interaction status records in the run record, and confirm that the same session does not repeatedly enter the interaction and that the process does not stop after the interaction is completed.