What this category's data looks like
Vocational training subsidy application materials mainly consist of training class filing records, sign-in records, and completion assessment forms. Their sources are institutional declarations and process traces, and their update cadence changes with class sessions and assessment milestones. Class filing records include the course, number of participants, start and end dates, and approval signatures; sign-in records form daily attendance details and student signatures; completion assessment forms record scores, assessment dates, and assessor signatures. When entering workflow orchestration, the three types of materials respectively serve the roles of application basis, process proof, and result evidence, and their fields need unified naming, date, and quantity conventions in the version ledger.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "version ledger and change records" are continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state; after the selection is completed, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Training class filing record | Course name, declared number of participants, start and end dates, and approval signature are consistent between the filing record and sign-in records | Compare the fields, dates, and signatures of the filing form and sign-in records item by item, and check the filing version number referenced in variables |
| Sign-in record | Attendance dates, student names, and quantities correspond to the list in the completion assessment form, and receipts are complete | Check the sign-in details against the assessment form list day by day, and verify whether the sign-in version referenced by the node corresponding to nodeId is current |
| Completion assessment form | Assessment date, scores, and assessor signature are consistent with the filed course, and old versions are traceable | Check the course, dates, and signatures of the assessment form and filing, and confirm that references are updated synchronously and old versions are archived |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check whether the version number and references in each material are updated synchronously, and record the differences before and after the change |
Three common errors
- Symptom: The same student's name is written differently in the sign-in record and the completion assessment form, and the quantities do not match. Cause: The two materials are entered separately, and the field conventions are not unified through the version ledger.
- Symptom: The class filing record has been updated, but the sign-in record and assessment form still reference the old dates. Cause: The versions are not synchronized, and subsequent nodes do not re-reference the current version according to the branch.
- Symptom: The completion assessment form lacks the assessor's signature or receipt, and the application is returned. Cause: The material circulation step does not check the completeness of signatures and receipts, and change records are not retained.
How to verify the setup
This feature's acceptance: run through each option one by one, check the branch directions and interaction states in the run records, confirm that the selection result variables have been passed to subsequent nodes, and check whether the references in variables and nodeId point to the current version.
Business test: change one piece of content, see whether the version number and references are updated synchronously, and whether the old version is still traceable.
- At the user selection node, check the options and branch connections one by one, and after a trial run, view the node status and branch directions in the run records.
- Reference the selection result variable in subsequent nodes and perform a trial run to confirm that the version ledger and change records continue execution according to the branch and synchronously update references.