What this category's data looks like
Vocational training subsidy application materials are mainly the training class filing records, sign-in records, and completion assessment forms archived by this park. The class filing contains the institution name, occupational type of work, class start date, student roster, and filing receipt; the sign-in records contain daily attendance, sign-in handwriting, and lead instructor signature; the completion assessment form contains the assessment date, score column, assessor signature, and completion conclusion. The three types of materials are archived by class session, and versions are updated with corrections and reviews. The name, quantity, and date of the same record in two materials may not match; when versions are not synchronized or signatures/receipts are missing, it is necessary to refer back to the original text for verification. After the materials enter the workflow, the class filing is used to confirm the class session and personnel scope, the sign-in records are used to verify attendance and signatures, and the completion assessment form is used to determine completion and subsidy conditions, each participating in orchestration as the source of basis entries.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. Basis entries that can refer back to the original text are completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Training class filing | Fields include institution name, occupational type of work, class start date, student roster, and filing receipt; the date and signature must match the original text | Check the options and branch connections one by one in the node, reference variables to record the selection result, and after a trial run check the node status in the run records |
| Sign-in records | Fields include daily attendance, sign-in handwriting, and lead instructor signature; the name, quantity, and date of the same record in two materials must be consistent | Reference this variable in a subsequent node and run a trial once, check the branch direction corresponding to nodeId, and when signatures or receipts are missing, refer back to the original text for annotation |
| Completion assessment form | Fields include assessment date, score column, assessor signature, and completion conclusion; the version must be current and match the class filing | Trigger an interaction once, check whether variables are passed to subsequent nodes, and when dates and quantities do not match, record the discrepancy entries |
| Basis entry | The entry can refer back to the original text, the source is the institution’s materials, and the version is current | Check the interaction status and branch direction in the run records, and compare the original source item by item |
Three common errors
- Symptom: The name, quantity, and date of the same record in two materials do not match. Cause: Field definitions were not unified by class session during archiving, and corrections were not backfilled.
- Symptom: Versions are not synchronized, and an old filing and a new assessment form enter orchestration at the same time. Cause: The update cadence was not aligned with the review node, and version identifiers are missing.
- Symptom: Signatures or receipts are missing, and the sign-in records and completion assessment form cannot mutually corroborate each other. Cause: The signature column was not checked during material handover, and receipts were not archived with the class session.
How to verify the setup
This feature acceptance: run trials for each option one by one, check the branch direction and interaction status in the run records, and confirm that the branch connections corresponding to variables and nodeId are correct.
Business test: ask a cross-material basis question, see whether the answer gives a source that can be referred back to, and record the number of cited entries and quoteMaxToken separately.
- Check the options and branch connections one by one in the node, and after triggering an interaction once, check the node status and branch direction in the run records.
- Reference the selection result variable in a subsequent node and run a trial once, and check whether the date, quantity, signature, and receipt can be referred back to the original text.