What this category's data looks like
This page covers university employment signing and graduation destination statistics, handling three types of materials: employment agreements, graduation destination registration forms, and employer certificates. The employment agreement contains the employer name, unified social credit code, signing date, and signatures of both parties; the graduation destination registration form contains the destination type, employer name, reporting date, and department confirmation; the employer certificate contains the receiving position, onboarding date, and employer receipt. Material sources are department submissions, employment system exports, and employer returns. The update cadence is triggered by batches and signing changes, and old versions must be archived. The field characteristic is that the same record's name, quantity, date, and signature must be consistent across multiple materials, the version number increments as content changes, and references are refreshed in sync.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "version ledger and change records" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. Variables can be used as placeholders in all three places: the request URL, request headers, and request body. Variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | The employer name, signing date, and signature must be consistent with the registration form | In the request preview, check the rendered URL and request body fields, and compare the name, date, and signature between the agreement and the registration form |
| Graduation destination registration form | The destination type, reporting date, and department confirmation must be consistent with the agreement | Check the request header names and value sources, use a sample request to compare the returned fields, and confirm that the date and destination type are in sync |
| Employer certificate | The receiving position, onboarding date, and employer receipt must be consistent with the registration form | In the variables panel, check the source of each placeholder, and check whether the receipt field is updated with the version number |
| Version ledger | The current version is unique, old versions are traceable, and references are in sync | After changing one piece of content, resend the request and check whether the version number in the returned fields and the references are updated in sync |
Three common errors
- Symptom: The employer name and signing date for the same record do not match between the employment agreement and the registration form. Cause: The two were entered separately, were not verified against the same version number, and were not refreshed in sync after changes.
- Symptom: The employer certificate lacks a signature or receipt, yet the registration form shows it as confirmed. Cause: The receipt field was not updated with the material upload, the version was not synced, and the old version is still referenced.
- Symptom: The request returns 401, and the external system receives empty fields. Cause: The request header authentication information was not passed in as required by the external system, the request body fields are inconsistent with the agreement, and the variable placeholders were not parsed into actual values.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; at the same time, check the value sources and return structure of the three identifiers Authorization, variables, and responseData.
Business test: change one piece of content and see whether the version number and references are updated in sync
- In the request preview, check the rendered complete URL, request header names, and request body fields, and confirm that all placeholder variables can be parsed into actual values.
- In the variables panel, check the source of each placeholder, use a sample request to compare the response, and confirm that the version number and references are updated in sync.