What this category's data looks like
This page centers on the scenario of registration review for professional and technical personnel qualification examinations, handling the drafting and responsibility handover of three types of materials: registration forms, academic qualification certificates, and work experience certificates. The material sources are examination agency templates, academic degree information, and work experience statements issued by employers. The update cadence advances with registration batches and review milestones. Field characteristics center on name, ID number, education level, graduation date, position title, start and end dates, certifier signature, and receipt date. When materials enter workflow orchestration, the registration form assumes the role of the main record, while the academic qualification certificate and work experience certificate serve as attachment support fields. The three must keep names, quantities, and dates consistent on the same record, and clearly identify the drafter, reviewer, and recipient. Versions and dates are refreshed synchronously with each handover; if a signature or receipt is missing, the process must not proceed to the next stage.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Issuable material drafts and handover records" are completed by subsequent nodes continuing execution along the branches. 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 |
|---|---|---|
| Registration form | Fields complete, responsible parties clear, version and date consistent | Check the options and branch connections one by one in the node, and confirm whether the drafter and reviewer signature fields, version number, and date are synchronized |
| Academic qualification certificate | The name, quantity, and date of the same record do not match across the two materials | Reference variables in subsequent nodes and run a trial once, comparing whether the graduation date and education level are consistent with the registration form |
| Work experience certificate | Missing signature or receipt | Trigger once, check the node status in the run records, and confirm whether the certifier signature and receipt date are complete |
| Handover record | The process stops after the interaction is completed | Reference nodeId and variables in subsequent nodes, and verify whether the recipient, handover date, and branch direction correspond |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across the two materials. Cause: During drafting, field-by-field comparison was not performed against the registration form as the main record; the attachment and the main form were filled in separately.
- Symptom: Versions are not synchronized. Cause: After the academic qualification certificate or work experience certificate is updated, the registration form version number and date are not refreshed with the handover, and subsequent nodes still reference the old version.
- Symptom: Missing signature or receipt. Cause: The handover stage does not treat signature and receipt as release conditions; the node directly enters the next branch, and receipt information is missing.
How to verify the setup
This feature acceptance: Run trials for each option one by one, check the branch direction and interaction state in the run records, and confirm that the selection result variables have been passed to subsequent nodes.
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch and that no default branch is mistakenly taken.
- Reference
variablesandnodeIdin subsequent nodes, run a trial once, and record the tokens and array length of the referenced text.