What this category's data looks like
This page covers three types of materials in university employment signing and graduation destination statistics: employment agreements, graduation destination registration forms, and employer certificates. Employment agreements come from the signing stage between graduates and employers, and their update cadence advances with signing batches; graduation destination registration forms are filled in by students, reviewed by departments, and then aggregated, with an update cadence by month or by batch; employer certificates are issued by hiring units, and their update cadence follows the arrival of offer letters or acceptance letters. When these three types of materials enter workflow orchestration, the employment agreement takes on the role of field verification for the signing entity and breach clauses, the graduation destination registration form takes on the role of field verification for destination category and statistical scope, and the employer certificate takes on the role of supporting evidence for unit name, position, and acceptance date. Field characteristics are concentrated in names, quantities, dates, signatures, and receipts. The same record often has mismatched names, quantities, and dates across two materials, versions are not synchronized, and signatures or receipts are missing.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. Draft materials that can be issued and handover records are completed by subsequent nodes continuing execution according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | Fields are complete, the responsible person is clear, the version and date are consistent, and the name, quantity, and date match those in the graduation destination registration form and employer certificate | Check the options and branch connections one by one in the user selection node, trigger it once and view the node status in the run record, and reference variables in a subsequent node for a trial run |
| Graduation destination registration form | Fields are complete, the responsible person is clear, the version and date are consistent, and the name, quantity, and date match those in the employment agreement and employer certificate | Check the options and branch connections one by one in the user selection node, trigger it once and view the node status in the run record, and reference variables in a subsequent node for a trial run |
| Employer certificate | Fields are complete, the responsible person is clear, the version and date are consistent, and the name, quantity, and date match those in the employment agreement and graduation destination registration form | Check the options and branch connections one by one in the user selection node, trigger it once and view the node status in the run record, and reference variables in a subsequent node for a trial run |
| User selection node | Each option corresponds to one branch, the interaction state is recorded, and the selection result variable has been passed to subsequent nodes | Check the options and branch connections one by one in the node, trigger it once and view the node status in the run record, and reference nodeId and variables in a subsequent node and perform a trial run |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the employment agreement and the graduation destination registration form. Cause: The two materials are drafted in different stages, and the field sources are not checked in a unified way.
- Symptom: The versions of the employer certificate and the registration form are not synchronized, and the old version is still referenced. Cause: The version and date are not recorded during handover, and subsequent nodes continue execution according to the old branch.
- Symptom: Materials lack signatures or receipts, and the handover record is incomplete. Cause: The user selection node only records branch direction and interaction state, and signatures and receipts are not completed in subsequent nodes.
How to verify the setup
Acceptance for this feature: run trials option by option, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and reference variables and nodeId in a subsequent node for a trial run.
Business test: draft one copy 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, trigger it once, and then view the node status in the run record.
- Reference
variablesandnodeIdin a subsequent node and perform a trial run, checking the branch direction and interaction state record.