What this category's data looks like
This page addresses the scenario of credit management for primary and secondary school teacher training. The materials include three types: training notices, credit recognition forms, and participant lists. Training notices come from education authorities or school academic affairs offices, are updated by semester or project batch, and contain training name, start and end dates, target participants, number of class hours, and signature/seal fields; credit recognition forms are filled out by the training organizer or school and contain teacher name, ID document number, training project, recognized credits, recognition date, and review signature; participant lists are compiled by the project leader and contain name, unit, subject, participation status, sign-in, and receipt. When these three types of materials enter workflow orchestration, the notice serves as the entry point and basis for the authorization scope, the recognition form serves as the object of credit verification, and the list serves as the roster for visibility scope and identity matching. The three places most prone to issues are dates, signatures, and quantities, where the same record may not match across two materials, or versions may not be synchronized, or signatures and receipts may be missing.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Externally available entry points and authorization scope" are completed by subsequent nodes continuing execution according to the branch. When the user selection 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 |
|---|---|---|
| Training notice | Whether the training name, start and end dates, target participants, and signature/seal fields in the notice are consistent with the credit recognition form | Compare the name, dates, and signatures in the notice and recognition form item by item, check the options and branch connections, and confirm that the entry point and authorization scope are set according to the notice |
| Credit recognition form | Whether the recognized credits, recognition date, and review signature correspond to the participation status and receipt in the participant list | Check the options and branch connections one by one in the node, reference variables for a trial run, and view the node status and branch direction in the run record |
| Participant list | Whether the name, unit, subject, and participation status in the list are synchronized with the versions of the notice and recognition form | Trigger once, view the node status in the run record, and confirm that the branch corresponding to nodeId matches the visibility scope |
| User selection node | Whether each option corresponds to one branch, and whether execution continues downward after the interaction is completed | Reference the selection result variable in a subsequent node and run a trial once, checking the transfer of variables and nodeId |
Three common errors
- Symptom: The same teacher's name, class hours, or dates do not match between the notice and the recognition form. Cause: The two materials were filled out by different handlers and entered the workflow without cross-checking.
- Symptom: The participant list has been updated, but the notice is still the old version, causing the visibility scope to not match the authorization entry point. Cause: Versions were not synchronized, and the materials were not locked to the same batch.
- Symptom: The credit recognition form lacks a review signature or the participant list lacks a receipt, and the process stops after the interaction is completed. Cause: The materials are incomplete, and the branch conditions cannot be determined.
How to verify the setup
This feature acceptance: Run a trial for each option one by one, check the branch direction and interaction state in the run record, and confirm that variables and nodeId can be referenced in subsequent nodes.
Business test: Access once with a restricted identity, see whether the visibility scope matches the settings, and confirm that unauthorized content is not visible.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and continue downward execution after the interaction is completed.
- Reference the selection result variable in a subsequent node and run a trial once, checking whether the node status and branch direction in the run record are consistent.