What this category's data looks like
This category's data involves three core material types: the employment agreement, the graduation destination registration form, and the employer certificate. The employment agreement contains the employer name, unified social credit code, signing date, and signatures/seals of both the graduate and the employer; the graduation destination registration form contains the destination type, employer name, reporting date, and review signatures of the department and the school; the employer certificate contains the offered position, onboarding date, employer contact, and receipt. The three material types come from different sources: the agreement is signed by both the employer and the graduate, the registration form is filled in by the student and then reviewed level by level, and the certificate is issued separately by the employer. In terms of update cadence, agreements are archived in batches along with signing batches, registration forms are updated on a rolling basis according to the graduation destination confirmation cycle, and certificates are submitted sporadically according to when the employer issues them. In terms of field characteristics, the four field types—name, quantity, date, and signature—are the most prone to cross-material discrepancies, and after entering the workflow they respectively take on the roles of primary record, comparison record, and supporting record.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. "Basis items that can be traced back to the original text" are then completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | Whether the employer name, signing date, and signatures of both parties are consistent item by item with the registration form | Select the agreement branch in the node options, run a trial, then check the branch direction and interaction state in the run record, and use nodeId to locate it |
| Graduation destination registration form | Whether the destination type, reporting date, and review signature cover the agreement fields and whether the version is current | Select the registration form branch in the node options, run a trial, then check whether subsequent nodes reference the selection result variables and provide a traceable source |
| Employer certificate | Whether the position, onboarding date, and receipt signature match the agreement and registration form | Select the certificate branch in the node options, run a trial, then check whether the process continues after the interaction is completed and whether the branch is consistent with the selected option |
| Workflow node | Each option corresponds to one branch and records the interaction state when triggered | Run a trial for each option one by one, check the branch direction and interaction state in the run record, and check the passing of variables |
Three common errors
- Symptom: the same graduate's employer name is written differently in the agreement and the registration form. Cause: the two materials are entered separately by the employer and the department, and name normalization has not been performed.
- Symptom: the signing date in the agreement does not match the reporting date in the registration form. Cause: the registration form is updated on a rolling basis according to the confirmation cycle, and the agreement archiving batch has not been synchronized.
- Symptom: the employer certificate lacks a receipt signature or the registration form lacks a department review signature. Cause: no signature completeness check is set up in the material supplementary submission step.
How to verify the setup
This feature's acceptance: run a trial for each option one by one, check the branch direction and interaction state in the run record, and confirm that each option corresponds to one branch and that the selection result variables has been passed to subsequent nodes.
Business test: ask a cross-material basis question and see whether the answer provides a traceable source.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger the user selection node once, and view the node state and interaction state in the run record.