What the documents look like
Promotion registration centers on price, inventory, and campaign rhythm rather than advertising wording review. The activity registration form records the campaign name, the registered product, the activity price, and the registration window. The promotional price approval form records the proposed selling price, the calculation of the lowest final payable price, and the approval status. The inventory lock table records the quantity reserved for the campaign and the lock period. The activity review form records the actual transaction price, sales volume, and resource slot performance. These documents update weekly or per campaign.
ERP inventory and historical transaction prices supply the basis for calculation, but this page handles only whether a draft sentence is supported by the material. It does not handle inventory writes or price synchronization. Because the material focus is on price and inventory values, any drafted copy must stay within the numeric boundaries set by the registration form and the approval form.
Constraints at the workflow routing step
The form input node enters an interaction state when triggered, collects the required fields, and passes the collected information to later nodes after submission. The user selection node evaluates the user's choice and executes the corresponding "yes" branch. Both nodes record the workflow state and continue execution after the user completes the interaction.
For this task, workflow routing collects the material fields needed for the copy to be drafted and passes the collected result to a later retrieval or judgment node. Whether a draft sentence is supported by the material depends on whether the material text states the subject, object, price value, and validity scope that the sentence involves. Semantic recall and relevance scores in the retrieval library do not carry permission or entity isolation duties. Retrieval results must be compared item by item against the material text; a similarity score does not replace that comparison. Order writes, document backfill, and external status synchronization require a separate business interface or later process and are outside this page.
Hypothetical paper test case: the material text reads "Activity registration form: March 2025 spring campaign, product A, activity price 199 yuan, registration window 1 March 2025 to 7 March 2025; promotional price approval form: product A proposed selling price 199 yuan, approval status pending review." The draft sentence to be judged is "Product A spring campaign activity price 199 yuan, approval already passed." The subject is product A, the object is the spring campaign activity price, the status field is approval status, and the validity scope is the registration window. The approval status in the source text is pending review, while the draft sentence states approval already passed; the two values differ on the same field.
Configuration and implementation checks
The table below lists documented settings or implementation check items relevant to this feature and task, using the sample above. The values are starting points for this hypothetical trial only, used for comparison, and are not official defaults.
| Configuration item | Hypothetical starting point | Reason and comparison method |
|---|---|---|
| Form input node required fields | Product name, campaign name, activity price, approval status | The sample judgment needs subject, object, value, and status; a missing item prevents comparison |
| User selection node branches | Material supported, material not stated | Select the branch according to the comparison result between the draft sentence and the source text |
| Interaction state check | Record state and wait for submission after triggering | Compare with the interaction node behavior described in the documents; no separate switch is set |
| Output handoff check | Pass collected fields to the later judgment node | Compare each passed field against the fields the sample requires |
| Retrieval scope check | Limited to material libraries with access rights | Check the library identifier and material source; do not perform cross-model joint association |
| External operation division | Approval status change connects to a separate business interface | This page records status only; it does not execute approval or writes |
Three common errors
- Reading approval status "pending review" as "approval already passed." The input is the sample source text and the draft sentence; the comparison is the value of the approval status field; the observable result is that the two values differ and the draft sentence is not supported by the material.
- Using retrieval relevance in place of material comparison. The input is a similar fragment returned by retrieval; the comparison is whether the fragment states product A, activity price 199 yuan, and approval status; the observable result is that a similar fragment that does not state approval status cannot support the draft sentence.
- Treating the inventory lock table or historical transaction prices as the basis for activity price approval. The input is the inventory lock table and historical transaction prices; the comparison is whether either states the approval status of product A's activity price; the observable result is that neither states that status, and approval status still comes from the promotional price approval form.
How to verify the setup
- Input the sample source text and the draft sentence "Product A spring campaign activity price 199 yuan, approval already passed." Compare the approval status field: the source text is pending review, the draft sentence is approval already passed. The condition is met when the system outputs that the sentence is not supported by the material; if it outputs supported, the check fails.
- Input a fragment returned by retrieval and compare whether the fragment states all three items: product A, activity price 199 yuan, and approval status. The condition is met when all three are stated before entering the supported branch; a missing item enters the material-not-stated branch. An empty result can be checked against the downstream design using a paper input of [], without claiming that a fictional rule retrieval necessarily returns [].
- Input the two branch connections of the user selection node and compare whether the choice matches branch execution. The condition is met when selecting "material supported" executes the supported branch and selecting "material not stated" executes the not-stated branch. Verify branch connections one by one; do not guarantee a first hit or full recall.
The documented technical facts checked for this feature, used to identify relevant content in the documents, are: the form input node enters an interaction state when triggered, collects required information, and passes it to later nodes after submission; the user selection node executes the corresponding "yes" branch after the user makes a choice, and branch connections are verified one by one; interaction state recording is behavior of the interaction node and no global state-recording switch is set or claimed; output handoff passes collected information explicitly to later retrieval, judgment, or interface nodes, and output is compared item by item against input; order writes, document backfill, and external status synchronization require a separate business interface or later process.