What this category's data looks like
This category's data covers three types of materials: product manuals, sales talking points, and channel training schedules. Product manual fields include product name, version number, effective date, and signature block; sales talking points fields include scenario, talking points version, update date, and confirmation receipt; channel training schedule fields include course name, session number, start date, and instructor signature. The materials come from three parties: the product department, sales operations, and channel management, and the update cadence changes with product iterations and channel scheduling. When entering this feature, the product manual serves as the version baseline, while the sales talking points and the schedule serve as referencing parties, each carrying their own fields and signature information for subsequent comparison and synchronization.
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 by an external system as agreed and then completed. The HTTP module sends requests to the target address; path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Product manual | Whether the version number, effective date, and signature block match the ledger | Check the request body fields against the manual version fields, and compare the version number and date in the returned fields |
| Sales talking points | Whether the talking points version, update date, and confirmation receipt are synchronized | Check the authentication information in the request headers, compare the response with a sample request, and confirm the confirmation receipt field is not empty |
| Channel training schedule | Whether the course name, session number, and start date match the referencing party | Check the source of each placeholder in the variable panel, and confirm the session number and date fields render correctly |
| Request address and path parameters | Whether the placeholder variables can be resolved into actual values | View the fully rendered address in the request preview, and check the path parameter values |
Three common errors
- Symptom: the same product name is written differently in the manual and the sales talking points. Cause: the two materials maintain their fields separately and do not use the ledger as the single source of truth.
- Symptom: the sales talking points version has been updated, but the schedule still references the old version. Cause: the change record did not trigger reference synchronization, and the old version is traceable but not marked as invalid.
- Symptom: the schedule is missing the instructor signature or receipt. Cause: the material handoff step did not return the signature field, so subsequent nodes cannot verify it.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; pay attention to the values of Authorization, variables, and responseData.
Business test: change one piece of content and see whether the version number and references are updated in sync.
- In the variable panel, check the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or the output of preceding nodes. - Check the request header names and value sources, confirm that
Authorizationis passed in as required by the external system, and that theresponseDatafield in the response body matches the agreement.