What this category's data looks like
Vocational training subsidy applications involve three types of materials: training class filing, sign-in records, and completion assessment forms. Class filing includes institution name, occupational type of work, class start date, and approval signature; sign-in records include trainee name, ID number, sign-in date, and personal signature; completion assessment forms include assessment subject, score, assessment date, and assessor signature. When these three types of materials enter the scheduled tasks and automation function, class filing serves as the version master record, and sign-in records and completion assessment forms serve as attachments referencing the master record version number. The update rhythm is triggered by batch: filing is updated before each class starts, assessment forms are archived after completion, and sign-in records are summarized daily. Field characteristics require the same record to be consistent across materials in name, quantity, and date, and the version number to be refreshed synchronously with master record changes.
Configuration and implementation checks
This step is executed by trigger configuration and tool nodes (scheduled capability is not in the tool introduction), outputting trigger records and execution results. Trigger configuration is set according to class start and completion nodes, and tool nodes are responsible for pulling materials and comparing versions. The version ledger and change records are completed by business processing according to records or by supplementary runs, ensuring the current version is unique, old versions are traceable, and references are synchronized.
| Object | Check | Verification action |
|---|---|---|
| Training class filing | Institution name, occupational type of work, class start date, and approval signature are consistent across filing, sign-in records, and completion assessment forms | Retrieve the filing master record and the two attachments, compare name, quantity, and date field by field; check whether approval signatures and receipts are complete; record the version number and reference direction |
| Sign-in records | Trainee name, ID number, sign-in date, and personal signature are consistent across sign-in records and completion assessment forms | Summarize sign-in records daily and compare them item by item with the completion assessment form roster; check entries missing signatures or receipts; confirm that the referenced master record version number has not expired |
| Completion assessment form | Assessment subject, score, assessment date, and assessor signature are consistent across the assessment form and filing | Retrieve the assessment form and filing master record, check subject and date; check assessor signature and receipt; confirm that the version number and reference are updated synchronously |
| 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 increments, whether the old version is retained, and whether references are synchronized; check trigger records and execution time |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match across two materials. Cause: the materials are entered separately, are not uniformly referenced by the master record version number, and fields are not compared across materials.
- Symptom: the version is not synchronized, and the old version is still referenced. Cause: after a change, the reference direction is not refreshed, scheduled tasks do not cover attachment materials, and the ledger does not record the change.
- Symptom: missing signatures or receipts. Cause: sign-in records and completion assessment forms are not summarized and archived daily, the approval step is omitted, and trigger records are not marked for supplementary runs.
How to verify the setup
Acceptance of this function: check trigger records and execution time to confirm execution occurs on time and only once; check whether tool nodes are triggered according to the introduction, and whether the tool call termination node is connected when no summary is needed; check whether trigger records and execution results are complete.
Business test: change one piece of content and see whether the version number and references are updated synchronously; confirm that the current version is unique and old versions are traceable.
- Check the trigger configuration and process connections, confirm that the trigger is connected to the corresponding tool node, and view trigger records and execution time.
- Change one piece of filing content, and check whether the version number increments, whether the old version is retained, and whether references in sign-in records and completion assessment forms are updated synchronously.