What the documents look like
Price and display audits take place during day-to-day operations, where the focus is sustained execution of standards. The main data sources are the supervision system, POS price lists, store cameras and headquarters promotion schedules. The documents handled day to day are store visit photos, price tag lists, display standards and rectification notices. The typical parties involved are the chain operations department, regional supervisors and store managers. Data updates weekly and monthly.
In contract and transaction material comparison these materials play different roles. Store visit photos and price tag lists are on-site execution evidence. Promotion schedules and display standards are the basis of headquarters requirements. Rectification notices are the record used to track closure. Workflow routing has to bring these sources into interaction nodes, where a person checks the material and the flow continues.
Constraints at the workflow routing step
When the form input node triggers, the conversation enters an interaction state, the required information is collected, and after submission the information is passed to subsequent nodes. When the user makes a choice at the user selection node, the "yes" branch is executed. The interaction state record is behavior of the interaction node; no separate global state recording switch is set. Collected information must be passed explicitly to later retrieval, judgment or interface nodes, and output and input are compared item by item. Order writing, document backfill and external state synchronization require a separate business interface or a later flow. Retrieval and form collection do not constitute authorized execution. At operations handover, the authorization state of materials, actions and requests must be verified separately.
Hypothetical exercise sample: a chain brand operations department drafts the sentence "The March store visit photos for the East China region have been checked, price tags match the promotion schedule, rectification notices are closed, and the material can be submitted to the regional supervisor for confirmation." Two passages of source material are supplied for checking. The first is headquarters promotion schedule text: "March schedule is item A store price 9.9 yuan, execution period March 1 to March 31." The second is a store visit photo record: "On March 12 a store price tag for item A showed 9.9 yuan, photographed by the regional supervisor." The point to be judged is the status "rectification notices are closed" in the draft sentence. The available material does not state any issuance, reply or closure record for a rectification notice.
Configuration and implementation checks
| Configuration item | Use on this page | How to check |
|---|---|---|
| Form input node | Collect store visit photo number, price tag list version, promotion schedule number | After submission, compare each required field with the input of later nodes |
| User selection node | A person judges whether material is complete and selects a branch | Check that the "yes" branch connection matches the selection result |
| Interaction state check | Confirm the conversation enters the interaction state after triggering and records workflow state | Observe the appearance and resumption of the interaction state; do not assume snapshot protection |
| Output handover check | Pass collected information to retrieval, judgment or interface nodes | Compare node output with form input item by item |
| External action division | Order writing, document backfill and external state synchronization connect to a separate business interface | Check whether an interface node exists; do not assume automatic triggering |
| Hypothetical trial starting point | Before judging the draft sentence, set the "rectification notice status" field to pending verification | Compare with the source material; keep pending verification when no record exists |
Three common errors
- Treating a retrieval hit as authorized execution. Input is the draft sentence and the source material; compare the retrieval result with the authorization state field. A retrieval returning a relevant passage does not mean the regional supervisor has confirmed.
- Treating form collection as business verification. Input is the store visit photo number submitted in the form; compare whether a later node separately verifies that the photo and the price tag agree. The submission action itself does not complete verification.
- Treating pending review as absence of operating permission. Input is a rectification notice in pending review status; compare whether a separate permission record exists. Pending review does not establish absence of operating permission.
How to verify the setup
- Input the draft sentence and the two source passages from the hypothetical exercise sample; compare "rectification notices are closed" with whether the material contains any issuance, reply or closure record. When the material does not state this, the result should be pending verification.
- Input the promotion schedule text and the store visit photo record; compare the item A price field of 9.9 yuan with the price tag of 9.9 yuan in the photo. The condition is met when the same subject, the same period and the same field carry the same value.
- Input the store visit photo number submitted in the form; compare whether the input of later nodes matches that number, and check whether the "yes" branch connection executes according to the selection result. The condition is met when the branch connection matches the selection result.