<!-- Generated by scripts/export-user-manual.mjs from the rendered manual. Do not edit. -->

# Editor: add a choice and connect its outcome

Give learners another response: “Ask a supervisor”. Write the supervisor’s reply first, connect the new choice, then decide what happens after that reply.

## Pair the choice text with a destination

This example uses choice mode. “Ask a supervisor” is what the learner reads and selects; that choice’s Target identifies the next step. Placing a node on the canvas does not by itself create a route into it.

<a id="editor-practice"></a>

1. ### Place a response node

   

   Select Expand and interact. Under Add Node on the left, select VIEW and click an empty canvas area. On narrow screens on this page, open Add node tools first; in your own project, Add Node appears only on the Graphical Edit tab. In the selected node’s right panel, select Add Dialogue and enter “I will ask a supervisor to help confirm the next step.” Note the node ID in its heading.

   

   **Check the result：**A new VIEW appears with your reply. No choice leads to it yet.
2. ### Add the learner choice and its target

   

   Select I\_response. Under Choice List, select Add Choice and enter “Ask a supervisor”. Set Target in that same choice card to the new node’s ID.

   

   **Check the result：**I\_response has three choices. A connection labelled “Ask a supervisor” leads to the new VIEW. You do not need to drag another connection.
3. ### Choose what happens after the reply

   

   Select the new VIEW. At the bottom of the right panel, set Flow Control to I\_response so learners can choose again after the advice.

   

   **Check the result：**A connection leads from the new VIEW back to I\_response. The new choice now has both an outward and a return route.
4. ### Read all three routes

   

   Select I\_response and check “Check the policy → V\_help”, “Promise a refund → V\_retry” and “Ask a supervisor → new VIEW”. Then select V\_retry and the new VIEW to check that both return to I\_response.

   

   **Check the result：**Each choice has the intended text and target. The new route has not replaced either original route. Later, try all three answers in Simulation.

Each chapter starts with its own example. Edits and saves stay on this page. The instructions remain on the left when you expand the editor.

Want text entry, multiple selection or ordering?

An INTERACT node’s mode controls how learners answer; it is not an editor tab. The exercise uses choices with individual targets. Multiple selection, ordering and text entry also need a place to store the response and a route after submission.

| What learners should do | mode value | What to prepare |
| --- | --- | --- |
| Choose one response and see its consequence | `choice` | For example, check the policy or ask a supervisor. Each choice has its own target, as in this exercise. This is also the default when mode is absent. |
| Write a response and submit it | `text` | Ask learners what they would say to the customer. Set storage\_key to the answer variable, prompt to the question and placeholder to an input hint. Set the whole node’s next step after submission. |
| Select several facts to check, then submit | `multiselect` | For example, purchase date, item condition and proof of purchase. Prepare the options, storage\_key, min\_selection and a next step after submission. |
| Drag the entire set of actions into order | `order` | For example, arrange listening, checking and proposing a solution. Prepare the items, storage\_key and a next step after the ordered set is submitted. |
| Select actions in the intended sequence | `select_order` | For example, check purchase details, then the refund policy. Prepare the items, storage\_key, required\_count and a next step after submission. |
| Select several items drawn from a database | `random_multiselect` | Prepare the question database first. Set storage\_key, db (the database), pick\_count (items to draw) and answer (answer items), plus the next step after submission. |
| Select database-drawn items in sequence | `random_select_order` | Prepare the database and set storage\_key, db, pick\_count and answer. The response includes the learner’s selection order. Set a next step after submission. |

### Configure another mode in your project

1. #### Prepare the answer you want to collect

   

   Select an INTERACT node. Under Properties on the right, enter mode in New key, select + and enter a value from the table. Edit the existing value if mode is already present. Add the other properties required by that mode. Set storage\_key to an answer variable already defined in your project.
2. #### Set the whole node’s next step in Code

   

   Multiple selection, ordering and text entry do not use the single-choice pattern of a separate route per option. Select Code, find the INTERACT block and set its next step, for example -> V\_help. The right-hand INTERACT form currently has no node-level Flow Control field for this.
3. #### Validate, save and answer the question

   

   Select Validate and resolve missing properties or destinations, then save, build and play in Simulation. Multiple-selection and ordering answers need separate evaluation and feedback; changing mode does not create scoring. Check selection counts and submission rules during play rather than assuming min\_selection or required\_count alone establishes them.

What does dragging or deleting a connection change?

Dragging from VIEW or LOGIC changes its next step. Dragging from INTERACT adds a choice with empty text; fill it in on the right. Dragging from ROUTE adds a branch whose condition needs filling. To redirect an existing choice, change its Target. Clicking a connection clears targets pointing to that destination but keeps choice text. If several choices share that destination, check each of them. To stop after a reply, set that VIEW’s Flow Control to END.

After checking, the third choice should lead to the supervisor’s reply and return to the choice. This example does not carry into the next chapter; that chapter uses the opening dialogue to practise saving.

[Go to the next lesson](doc2sim-editor-save.md)
