What this category's data looks like
University employment contract signing and graduation destination statistics are based on three types of materials: employment agreements, graduation destination registration forms, and employer certificates. Employment agreements contain the employer name, position, signing date, and signatures of both parties; graduation destination registration forms contain the destination category, employer nature, reporting date, and department seal; employer certificates contain the offer letter, receipt confirmation, and contact person. Materials enter the workflow weekly or in batches, and the update rhythm is synchronized with the signing progress. When entering this function, the three types of materials each assume different roles: employment agreements serve as the baseline record of the signing fact, graduation destination registration forms serve as the mapping basis for destination classification and statistical criteria, and employer certificates serve as supplementary evidence for receipt and signature completeness. Field characteristics are concentrated in four areas: employer name, quantity, date, and signature receipt. Before statistics, the criteria must first be unified and written into the header.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "Progress Table and Statistical Criteria Description" is continued and completed by subsequent nodes according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | Whether the employer name, signing date, and signatures of both parties are consistent with the registration form, and whether the name and date of the same record match across the two materials | Compare employer names and signing dates one by one, and separately mark those missing signatures or receipts; check the options and branch connections in the node, and confirm that variables has been passed to subsequent nodes |
| Graduation destination registration form | Whether the destination category and statistical criteria are written into the header, whether the reporting date and department seal are complete, and whether the version is synchronized | Summarize the number of records according to the header criteria, and verify the quantity and dates one by one against the agreements; view the node status corresponding to nodeId in the run records |
| Employer certificate | Whether the receipt confirmation and contact person are complete, and whether the name, quantity, and date of the same record are inconsistent with the other two materials | Extract the receipt and contact person fields, and cross-check them against the agreement and registration form; run a test once to confirm that the selection result variable has been passed to subsequent nodes |
| Progress table and statistical criteria description | Whether the number of records matches the statistical count, and whether the criteria and exceptions are clearly stated | Use one week of records to verify the totals, write the criteria and exceptions into the header, and fall back to the corresponding materials to fill in missing items |
Three common errors
- Phenomenon: The employer name, quantity, and date of the same record are inconsistent between the employment agreement and the graduation destination registration form. Cause: The two materials are entered separately without cross-verification, and the criteria are not unified before statistics.
- Phenomenon: Material versions are not synchronized, and an old version of the registration form is still included in the totals. Cause: The update rhythm is disconnected from the signing progress, and the version identifier is not updated as materials flow.
- Phenomenon: The employer certificate lacks a signature or receipt, so the record cannot be included in the statistics. Cause: Receipt collection and signature confirmation are not included in the progress table, and exceptional cases are not stated in the header.
How to verify the setup
This function's acceptance: run tests option by option, check the branch directions and interaction states in the run records, and confirm that options correspond to branches, interaction states are recorded, and selection result variables have been passed to subsequent nodes.
Business test: use one week of records to verify the totals, check whether the criteria and exceptions are clearly stated, and whether the number of records matches the statistical count.
- Check the options and branch connections one by one in the node, trigger once, then view the node status in the run records, and confirm that the
nodeIdandvariablesreferences are correct. - Summarize the three types of materials weekly, compare employer names, quantities, dates, and signature receipts one by one, write the criteria and exceptions into the header, and then include them in the weekly or monthly report.