What this category's data looks like
The main materials for university employment signing and graduation destination statistics are employment agreements, graduation destination registration forms, and employer certificates. The employment agreement is signed by the student and the employer and then returned; the graduation destination registration form is filled in by the student and preliminarily reviewed by the department; the employer certificate is issued by the employer with a receipt attached. Material sources are scattered, and the update rhythm is weekly aggregation and monthly verification. The field characteristics center on employer name, position, signing date, signature, and receipt status. When entering the progress record and statistical verification function, the employment agreement serves as the basis for signing, the graduation destination registration form serves as the basis for destination classification, and the employer certificate serves as supplementary evidence. Together, the three support the progress table and the explanation of statistical criteria.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "progress table and explanation of statistical criteria" is parsed from the response by subsequent nodes, or handled and completed by an external system according to the agreement. The HTTP module sends a request to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers.
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | Whether the fields, dates, and signatures are consistent with the graduation destination registration form | In the request preview, view the complete rendered address, verify the sources of Authorization and variables, and then compare the response against one sample |
| Graduation destination registration form | Whether the name, quantity, and date match the employer certificate | Verify the request header names and value sources, and check whether the fields returned in responseData include the key items of the registration form |
| Employer certificate | Whether the receipt is complete and whether the version is synchronized | Use one sample request to compare the response, confirm empty fields and timeout situations, and then proceed to the weekly or monthly report |
| Progress table and explanation of statistical criteria | Whether the record count matches the statistical count and whether the criteria are written in the table header | Use one week of records to verify the totals, and check whether the criteria and exceptions are clearly stated |
Three common errors
- Symptom: The employer name and signing date for the same record do not match between the employment agreement and the graduation destination registration form. Cause: The two materials were filled in at different times, and version synchronization and field comparison were not performed.
- Symptom: The employer certificate lacks a signature or receipt, but it is counted as signed during statistics. Cause: The material collection status was not marked in the progress table, and the criteria did not specify exception handling.
- Symptom: The request returns 401, or the external system receives empty fields or the request times out. Cause: The authentication information and variable sources were not verified, and the request body fields are inconsistent with the external interface agreement.
How to verify the setup
Acceptance for this function: preview the rendered request, verify the status code and returned fields, and then compare the result against one sample; check whether Authorization, variables, and responseData appear as agreed.
Business test: use one week of records to verify the totals, and check whether the criteria and exceptions are clearly stated.
- In the variables panel, verify the source of each placeholder and confirm that the variables in the path parameters, request headers, and request body can be resolved into actual values.
- Use one sample request to compare the response, verify that the request body fields are consistent with the external interface agreement, and record the number of array entries and the tokens budget of the referenced text.