What this category's data looks like
This page addresses Q&A intake and missing-item follow-up for social evaluation of vocational skill level certification. The materials come from three types: the evaluation implementation plan, the candidate registration form, and the assessor dispatch form. The evaluation implementation plan provides the certified occupation, level, and process framework; the candidate registration form carries the candidate's identity, application conditions, and contact information; the assessor dispatch form records assessors, dates, and signed receipts. When the three types of materials enter the function, each plays a different role: the implementation plan serves as the basis for judgment, while the registration form and dispatch form serve as objects to be verified, used to identify missing items and generate follow-up questions. The materials are updated by batch, and their field characteristics are concentrated in names, quantities, dates, and signature fields. The same record often shows mismatches in name, quantity, or date between two materials, or unsynchronized versions, missing signatures, and missing receipts.
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 records and the completed follow-up items are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the process. Variables can be used as placeholders in all three places: path parameters, request body, and request headers. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Evaluation implementation plan | Whether the fields, dates, and signatures are consistent with the registration form and dispatch form | Compare the occupation name, level, certification date, and approval field item by item, and record the locations of discrepancies |
| Candidate registration form | Whether the names, quantities, and dates can be aligned with the implementation plan and dispatch form | Extract the candidate name, application level, and registration date, and cross-check them against the other two materials |
| Assessor dispatch form | Whether the signatures and receipts are complete and whether the versions are synchronized | Check the assessor names, dispatch dates, signature fields, and receipts, and mark missing items |
| HTTP request | Whether the placeholders in path parameters, request headers, and request body can be resolved into actual values | View the fully rendered address in the request preview, and verify the sources of Authorization and variables |
Three common errors
- Symptom: The name or application level of the same candidate does not match between two materials. Cause: The registration form and the implementation plan are not synchronized, and the field definitions are inconsistent.
- Symptom: The assessor dispatch form lacks signatures or receipts, and they still cannot be completed after follow-up. Cause: The material circulation step did not return them, and the versions are not synchronized.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The source of the
Authorizationvalue is incorrect, or the request body fields are inconsistent with the external interface agreement.
How to verify the setup
Preview the rendered request, check the status code and returned fields, and then compare the responseData result against a sample.
Business test: submit a question that lacks key information and see whether it asks a follow-up question before answering.
- In the variable panel, verify the source of each placeholder and confirm that the path parameters, request headers, and request body can all be traced to global variables, system variables, or the output of preceding nodes.
- Use a sample request to compare the returned fields with the external interface agreement, and check whether
Authorization,variables, andresponseDataare consistent.