What this category's data looks like
This page addresses the scenario of question intake and missing-item follow-up for enterprise compliance and safety training. Materials include three categories: compliance training courseware, safety operating procedures, and exam records. Courseware is used to confirm the course name, version date, and applicable positions; procedures are used to verify operating steps, effective date, and signature fields; exam records are used to compare personnel lists, scores, dates, and receipts. Materials are updated in batches, and common fields include material name, quantity, date, version number, signature, and receipt. When entering this function, courseware and procedures serve as the basis for follow-up questions, and exam records serve as the source for missing-item determination. Together, the three support the intake record and the items to be completed.
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 "intake record and items to be completed" are parsed by subsequent nodes from the response, or handled by an external system according to the agreement to complete the process.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | The courseware name, version date, and applicable positions are traceable in the intake question items | Verify the courseware fields and dates, and compare whether the names and versions in the two materials are consistent |
| Safety operating procedures | The procedure steps, effective date, and signature fields can be referenced in follow-up questions | Check whether signatures or receipts are complete, and use a sample request to compare the returned fields |
| Exam records | The personnel list, scores, dates, and receipts can be matched in the missing-item determination | Verify the quantity and dates, and confirm whether the same record matches in the two materials |
| HTTP request configuration | Placeholders in path parameters, request body, and request headers can be resolved into actual values | Verify the source of variables in the variable panel, and preview the rendered URL and request header Authorization |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match in the two materials. Cause: The courseware and exam records were not updated synchronously in the same batch, and the field value sources differ.
- Symptom: The version is not synchronized, and the follow-up question references an old version of the procedure. Cause: After the material was updated, the intake process was not re-entered, and the placeholder variables still point to the old output.
- Symptom: A signature or receipt is missing, but the intake record is still transferred out. Cause: The missing-item determination does not cover the signature field, and the follow-up step did not first ask for the key information.
How to verify the setup
Acceptance for this function: preview the rendered request, verify the status code and returned fields, then compare the result against one sample; at the same time, verify the value sources of responseData and variables.
Business test: submit a question that lacks key information, see whether it asks a follow-up question before answering, and confirm that the missing item is identified and followed up on, and that the answer is based on materials.
- In the variable panel, verify the source of each placeholder, and confirm that the variables in the path parameters, request body, and request headers can be resolved into actual values.
- Use one sample request to compare the returned fields and status code, and check whether the external system receives empty fields or returns 401.