What this category's data looks like
This page addresses Q&A intake and missing-item follow-up for university employment signing and graduation destination statistics, involving three types of materials: employment agreements, graduation destination registration forms, and employer certificates. The employment agreement is signed by the student and the employer, and its fields include the employer name, unified social credit code, signing date, and signatures of both parties; the graduation destination registration form is compiled by the department, and its fields include destination type, employer location, reporting date, and department seal; the employer certificate is issued by the employer, and its fields include position name, number of hires, date of issuance, and official seal. The three types of materials come from different sources and are updated at different paces, and each plays a different role when entering Q&A intake: the employment agreement is used to verify the signing entity and date, the graduation destination registration form is used to verify the destination category and reporting information, and the employer certificate is used to verify the position and number of hires. The names, quantities, and dates of the same record across the three materials must be compared item by item; missing items and inconsistencies are first followed up on before answering, and are ultimately forwarded to the handler.
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 intake record and the completed follow-up questions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the process.
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | Check whether the employer name, signing date, and signature fields are consistent with the registration form | Compare the employer name and signing date between the employment agreement and the graduation destination registration form field by field, and check whether any signature field is missing |
| Graduation destination registration form | Check whether the destination type, reporting date, and department seal correspond to the agreement | Compare the destination type and reporting date, and check whether the department seal and receipt are complete |
| Employer certificate | Check whether the position name, number of hires, date of issuance, and official seal match the other two materials | Compare the position name and number of hires, check the date of issuance and official seal, and flag records whose quantity or date does not match |
| Request URL and path parameters | Placeholder variables can be resolved into actual values | View the fully rendered URL in the request preview, and check the source of variables and the value of Authorization |
Three common errors
- Symptom: The employer name and number of hires for the same record do not match between the employment agreement and the graduation destination registration form. Cause: The two materials are filled in at different stages, and no field-by-field comparison was performed.
- Symptom: The date of issuance on the employer certificate is inconsistent with the signing date on the agreement, and the versions are not synchronized. Cause: After one material was updated, the other was not written back, resulting in a date mismatch.
- Symptom: The employment agreement is missing a signature or the graduation destination registration form is missing a receipt, yet the answer is still given based on the original record after follow-up. Cause: Missing-item identification does not cover the signature and receipt fields.
How to verify the setup
Feature acceptance: preview the rendered request, check the status code and returned fields, then compare the results against one sample to confirm that responseData and variables are traceable.
Business test: submit a question that lacks key information and see whether it is followed up on before being answered.
- In the variables panel, check the source of each placeholder and confirm that both
variablesandAuthorizationcan be traced to a specific origin. - Use one sample request to compare the returned fields, check that the request body fields are consistent with the external interface agreement, and record the number of array items and the tokens of the referenced text.