What this category's data looks like
In the enterprise sales product training scenario, materials mainly come from three categories: product manuals, sales sales language, and channel training schedules. Product manuals are updated by the product department according to the version cadence, and their fields include product name, specification quantity, effective date, and version number; sales sales language is iterated quarterly by sales operations, and its fields include sales language number, corresponding product name, applicable date, and signature field; channel training schedules are published by the training team according to the schedule, and their fields include course name, number of participants, course start date, and receipt signature. When these three categories of materials enter workflow orchestration, the product manual serves as the baseline object, while sales sales language and channel training schedules serve as the objects to be verified, respectively taking on the roles of field comparison, date comparison, and signature receipt checking, forming the raw input for the discrepancy list.
Configuration and implementation checks
This step is executed by the workflow node (user selection and branching), outputting the branch direction and interaction status record. The "discrepancy list" is then completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters the interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Product manual | Whether fields, dates, and signatures are consistent with sales sales language | Compare product name, quantity, effective date, and signature field one by one, mark inconsistent fields, and record nodeId |
| Sales sales language | Whether fields, dates, and signatures are consistent with channel training schedule | Check the name, quantity, and date of the same record, inspect the version number and receipt signature, and reference variables to record discrepancies |
| Channel training schedule | Whether the version is synchronized and whether receipts are complete | Compare the version number and course start date of the schedule and sales language, check signature receipts, and output the branch direction |
| Discrepancy list | Whether it covers the three types of inconsistency: name, quantity, and date | Summarize the comparison results of each material, mark items with unsynchronized versions and missing signatures, and submit to the reviewer for confirmation |
Three common errors
- Phenomenon: The name and quantity of the same record do not match between the product manual and sales sales language. Cause: The two materials are maintained separately, and the field source and update entry point are not unified.
- Phenomenon: The version numbers of the channel training schedule and sales sales language are inconsistent. Cause: The versions are not synchronized, and old-version materials are still in circulation and use.
- Phenomenon: Materials lack signatures or receipts. Cause: The verification step does not enforce checking the signature field, and receipts are not archived together with the materials.
How to verify the setup
Feature acceptance: Try running each option one by one, check the branch direction and interaction status in the run record, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business test: Use one real record to find fields inconsistent with the ledger, record the three types of discrepancies in name, quantity, and date, and submit to the reviewer for confirmation.
- In the node, check the options and branch connections one by one, confirm that each option corresponds to one branch, and trigger once to view the node status in the run record.
- Reference the selection result variable in a subsequent node and run it once to confirm that the process continues downward after the interaction is completed, without stopping or repeatedly entering the interaction.