What this category's data looks like
Occupational skill level certification social evaluation involves materials such as evaluation implementation plans, candidate registration forms, and assessor dispatch forms. These materials come from internal preparation and external submission by evaluation institutions, and need to be updated by batch and maintained in a version ledger. The evaluation implementation plan includes the evaluated occupation, level, subjects, date, and evaluation method; the candidate registration form includes name, ID number, declared level, years of work experience, and signature; the assessor dispatch form includes assessor name, certificate number, dispatch date, and signature. When the materials enter the HTTP interface, the evaluation implementation plan serves as the main request body, while the candidate registration form and assessor dispatch form are referenced as attachment fields or path parameters, each playing a different role. The update rhythm is triggered by policy adjustments or batch changes, requiring the current version to be unique, old versions to be traceable, and references to be synchronized.
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 version ledger and change records are parsed from the response by subsequent nodes, or handled externally by an external system according to the agreement. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Evaluation implementation plan | Fields, dates, and signatures must be consistent with the candidate registration form and assessor dispatch form | Check the occupation name, level, evaluation date, and signature field in the plan, and compare the corresponding fields in the registration form and dispatch form |
| Candidate registration form | If the name, quantity, or date does not match the implementation plan or dispatch form, it is inconsistent | Extract one registration record, find a record with the same name and quantity in the implementation plan and dispatch form, and check the date and signature receipt |
| Assessor dispatch form | The dispatch date and number of assessors must be synchronized with the implementation plan and registration form | Check the signature and receipt on the dispatch form, and verify whether the version number is consistent with the current implementation plan |
| Request URL and path parameters | Placeholder variables can be resolved into actual values | View the fully rendered URL in the request preview |
Three common errors
- Symptom: The same candidate name is written differently in the registration form and dispatch form. Cause: The two materials were entered separately, without field alignment and version synchronization.
- Symptom: The evaluation date differs by several days between the implementation plan and the registration form. Cause: The versions were not synchronized, and the old version reference was not updated, causing the dates to mismatch.
- Symptom: The assessor dispatch form is missing a signature or receipt. Cause: The external system did not return it as agreed, and the HTTP node only outputs the response body and status code.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, then compare the result against one sample. Check the Authorization request header, the source of variables, and the responseData returned fields.
Business test: change one piece of content and see whether the version number and references are updated synchronously
- In the variables panel, check the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or outputs from preceding nodes - Use one sample request to compare the response, check that the
responseDatafields are consistent with the external interface agreement, and record the number of array items