What this category's data looks like
This page focuses on the university employment signing and graduation destination statistics category. Materials include employment agreements, graduation destination registration forms, and employer certificates. Employment agreements are used to confirm the signing entity and effective date, graduation destination registration forms are used to archive destination category and registration information, and employer certificates are used to corroborate the fact of hiring and signatures/seals. The three types of materials come from departmental submissions, employer returns, and school-level review, and the update cadence rolls forward with signing batches and graduation destination confirmation milestones. Field characteristics center on names, quantities, dates, and signature receipts: the names, quantities, and dates of the same record across the three materials must be consistent, versions must be synchronized, and signatures or receipts must not be missing. When materials enter the workflow, the employment agreement serves as the basis for the signing branch decision, the graduation destination registration form serves as the basis for the destination visibility scope, and the employer certificate serves as the basis for external service corroboration.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The externally available entry points and authorization scope are completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | Whether the signing entity, effective date, and signature are complete, and whether the name and quantity are consistent across the three materials | Check the options and branch connections one by one in the node, trigger a run to view the node status in the run records, and reference variables in subsequent nodes for a trial run |
| Graduation destination registration form | Whether the destination category, registration date, and version are synchronized, and whether it still enters the external branch when a signature or receipt is missing | Check the options and branch connections in the node, use nodeId to locate the node, and trigger a run to view the node status in the run records |
| Employer certificate | Whether the employer name, hiring quantity, and signature/seal date match the employment agreement and graduation destination registration form | Reference variables in subsequent nodes for a trial run, and check whether the material fields match the branch direction |
| Externally available entry points and authorization scope | Whether the visitor identity matches the visible scope, and whether unauthorized access is invisible | Access once with a restricted identity and see whether the visible scope matches the settings |
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 entered separately by different nodes, lacking cross-material comparison and version synchronization.
- Symptom: The employer certificate is missing a signature or receipt but still enters the external branch. Cause: The branch decision only looks at options and does not treat signature receipts as a material completeness condition.
- Symptom: After selecting an option, it still follows the default branch. Cause: The options and branch connections were not checked item by item, and after the interaction completes the process stalls or the same session repeatedly enters the interaction.
How to verify the setup
Feature acceptance: trial run each option one by one, check the branch direction and interaction state in the run records, confirm that options and branches correspond one-to-one, and use nodeId to locate the node and variables to check whether the selection result variable is passed to subsequent nodes.
Business test: access once with a restricted identity and see whether the visible scope matches the settings.
- Check the options and branch connections one by one in the node, and trigger a run to view the node status in the run records.
- Reference the selection result variable in subsequent nodes and trial run once to confirm that the branch direction is consistent with the interaction state records.