What this category's data looks like
This page covers three types of materials in university employment contract signing and graduation destination statistics: employment agreements, graduation destination registration forms, and employer certificates. Employment agreements are signed between graduates and employers, with fields including employer name, unified social credit code, signing date, and signatures and seals of both parties; graduation destination registration forms are compiled by departments, with fields including destination type, employer name, reporting date, and department review signature; employer certificates are issued by employers, with fields including receiving position, receiving date, employer contact, and receipt. Material sources are divided into online submission and offline paper return; the update rhythm changes with signing batches, supplementary entries, and contract modifications, and the name, quantity, and date of the same record in the three materials must be aligned item by item. When materials enter workflow orchestration, each serves as input for branch judgment and status recording: agreements and registration forms are used to verify the signing entity and destination type, employer certificates are used to verify receiving information and receipts, and those missing signatures or receipts enter the correction branch.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. "Handover-ready deployment status and operation records" are completed by subsequent nodes continuing execution according to the branches. When a user selection node is triggered, the conversation enters an interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | Whether the employer name, signing date, and signatures of both parties are consistent in the two materials | Check the options and branch connections one by one in the node, compare the employer name, signing date, and signature fields in the agreement and registration form, and use variables to record discrepancies |
| Graduation destination registration form | Whether the destination type, reporting date, and department review signature are complete | Trigger a user selection node once, check the node status in the run record, and verify whether the reporting date and destination type in the registration form and employer certificate are aligned |
| Employer certificate | Whether the receiving position, receiving date, and employer receipt are missing items | Reference the selection result variable in a subsequent node and run a trial once, check the receiving date and position name in the certificate and agreement, and route those missing receipts to the correction branch |
| Workflow node | Whether options and branch connections correspond one-to-one, and whether the interaction status is recorded | Check the options and branch connections in the node, use nodeId to locate the node, and view the interaction status and branch direction in the run record |
Three common errors
- Symptom: The employer name and signing date of the same record do not match between the agreement and the registration form. Cause: The two materials are entered in different stages; after a contract modification, only one is updated, and the versions are not synchronized.
- Symptom: The employer certificate is missing the employer receipt or the department review signature. Cause: Paper return and online submission run in parallel, the correction branch is not triggered, and the material does not flow back to the verification node.
- Symptom: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked item by item, and the selection result variable was not passed to subsequent nodes.
How to verify the setup
Acceptance of this feature: Run a trial for each option, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, the interaction status is recorded, and the selection result variable has been passed to subsequent nodes.
Business test: Check each item once according to the handover list, see which record is missing, and compare the fields, dates, and signatures of the employment agreement, graduation destination registration form, and employer certificate.
- Check the options and branch connections one by one in the node, use
nodeIdto locate the node, and confirm that each option corresponds to one branch. - Trigger a user selection node once, check the node status in the run record, reference the selection result variable in a subsequent node, and run a trial once.