What the documents look like
Creator-led sales campaigns rest on external creator performance and commission settlement. Brand-side shift scheduling does not sit at the centre of this category. The store service and internal training stage handles four document types: creator cooperation agreements, commission setting sheets, sample shipment sheets and live session reports. These record the cooperating parties, the commission basis, where materials went and how a session turned out. Creator historical data, the selected alliance, the creator marketplace and store transaction details provide outside reference points, yet this page stays with workflow routing itself. Materials update per session and per week; the update rhythm does not change how interaction nodes and downstream connections are checked here.
Constraints at the workflow routing step
In FastGPT v4.17.2, workflow routing realises user interaction through the Form Input node and the User Selection node. After either node triggers, the conversation enters an interaction state, the workflow state is recorded, and execution continues once the user finishes interacting. The Form Input node collects required information and passes it to later nodes after submission. The User Selection node judges the user's choice and executes the corresponding "yes" branch. Handover material for store service and internal training therefore has to be split along this mechanism: which items a form collects, which decisions a user selection branch handles, and which actions require a separate business interface or a later process. Retrieval and form collection do not themselves constitute authorisation; order writes, document backfill and external status synchronisation must be carried by downstream implementation.
Hypothetical paper exercise: a brand business representative submits a Creator Session Cooperation Handover Sheet. The source text reads: "Cooperating creator: Studio A; session: 14 June 2025 feature session; commission setting sheet status is awaiting review by the business lead; sample shipment sheet status: dispatched, recipient has not confirmed receipt." A draft sentence is submitted alongside it: "The commission setting for this session is confirmed, store training scheduling can be arranged." The request to be judged is: "Please route the training notification workflow according to this handover sheet."
Configuration and implementation checks
The table below centres on that sample and lists documented settings or implementation checks tied to this feature and the primary task. The values are hypothetical starting points for this exercise, used for comparison, and are not official defaults.
| Configuration item | Hypothetical starting point for this exercise | Reason and comparison method |
|---|---|---|
| Form Input node fields | Cooperating creator, session date, commission setting sheet status, sample shipment sheet status | Fields match the four source items; compare each submitted value against the handover sheet text |
| User Selection node branch | One "yes" branch for entering training scheduling | The document states the "yes" branch executes after a user choice; verify each branch connection |
| Interaction state check | Enters interaction state after trigger, records workflow state | Check node behaviour; no separate global state-recording switch is set |
| Output connection check | Form information passed to later retrieval, judgement or interface nodes | Compare output against input item by item and confirm the receiving node is specified |
| External action split | Training notification sending and scheduling writes attach to a separate business interface | The document does not state that nodes perform external writes automatically; a later process must carry them |
| Pending review handling | When commission setting sheet status is pending review, the "yes" branch is not entered | Pending review does not constitute approval; compare the branch condition against the source status |
Three common errors
- Treating "awaiting review by the business lead" as confirmed. The source text states the commission setting sheet status is pending review, while the draft sentence says the commission setting is confirmed. The comparison is the same field with the same value; pending review and confirmed are mutually exclusive, and the draft sentence is unsupported.
- Treating "dispatched, recipient has not confirmed receipt" as a signed-for sample. The sample shipment sheet status reaches dispatch only; receipt is a separate fact. If the workflow arranges store training material counting on that basis, the receipt evidence is absent.
- Treating the "yes" branch of the User Selection node as authorised execution. A user choice only triggers branch judgement; order writes, training notification sending and scheduling backfill require a separate business interface. Equating branch execution with a completed business action skips the downstream implementation.
How to verify the setup
- Input the four source fields and the draft sentence, then compare the commission setting sheet status field: the source reads pending review, the draft reads confirmed. The observable result is that the two are mutually exclusive on the same field, the draft sentence is judged unsupported, and the workflow must not enter the training scheduling "yes" branch.
- Input the sample shipment sheet status "dispatched, recipient has not confirmed receipt" and compare whether the workflow requires receipt evidence. The observable result is that the receipt fact is missing; if the process needs receipt to advance, record the evidence gap and keep the item pending verification.
- Input an explicit paper empty result [] and check whether the downstream connection design handles empty values. The observable result is whether the downstream node gives a clear branch or records a gap for empty input; no claim is made that a fictional rule retrieval necessarily returns []. Libraries across different vector models cannot be associated together; check identifiers first, exclude those that do not match, and record the actual observation.