What this category's data looks like
This page addresses progress records and statistics verification for enterprise sales product training; the materials come from three categories: product manuals, sales terminology, and channel training schedules. Product manuals provide fields such as product name, functional modules, version number, and effective date; sales terminology provides sales terminology number, applicable product, usage scenario, and revision date; channel training schedules provide course number, participating channel, teaching date, number of class hours, and signature field. The three categories of materials are updated weekly and summarized monthly. When entering this function, the product manual serves as the field baseline, while sales terminology and schedules serve as the sources of progress records, each carrying name, quantity, date, and signature information for subsequent statistics verification and specification explanation.
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 "progress table and statistics specification explanation" is parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the next step.
| Object | Check | Verification action |
|---|---|---|
| Product manual | Whether the name, version number, and effective date are consistent with the sales terminology and schedule | Take the product name and version from the manual, compare them item by item with the corresponding fields in the sales terminology and channel training schedule; verify the value source of variables in the request preview |
| Sales terminology | Whether the sales terminology number, applicable product, revision date, and quantity match | Group records by sales terminology number, verify the name, quantity, and date of the same product in the two materials; check whether the Authorization request header is passed in according to the external system's requirements |
| Channel training schedule | Whether the course number, teaching date, number of class hours, and signature field are complete | Sort by course number and teaching date, verify entries missing signatures or receipts; use a sample request to compare the responseData returned fields with the schedule records |
| Statistics specification explanation | Whether the record count and statistics count match, and whether the specification is written in the header | Write the statistics scope, exceptions, and cutoff date in the header, verify the total with one week's records; confirm that the request body fields are consistent with the external interface agreement |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the product manual and the sales terminology. Cause: The two materials are revised separately and are not updated in sync under the same version number.
- Symptom: The channel training schedule has class hour records but lacks participation signatures or receipts. Cause: When summarizing the schedule, only quantities are counted, and the signature field is not verified as a required item.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: Authentication information is not passed in according to the external system's requirements, or placeholder variables are not parsed into actual values.
How to verify the setup
This function's acceptance: preview the rendered request, verify the status code and returned fields, then compare the result against a sample; confirm that the values and sources of Authorization, variables, and responseData are consistent.
Business test: verify the total with one week's records, check whether the specification and exceptions are clearly written, and confirm that the record count and statistics count match.
- In the variables panel, verify the source of each placeholder, and confirm that the placeholder variables in the request URL, request headers, and request body can be parsed into actual values.
- Group one week's records by product name, sales terminology number, and course number, verify the name, quantity, date, and signature, and write exceptions into the header of the specification explanation.