Project Actions

The Project group holds actions that structure the scenario itself rather than drive the robot.

note

Section and Comment moved here from Flow, and Import Scenario from Import. Input Form is new.

Section

Groups related actions under a collapsible header. Pinned action.

Sections are the main tool for keeping a long scenario readable: collapse the parts you are not working on, and run a single section on its own while developing.

📸 Screenshot needed — /img/editor/actions/project/section.png

Capture: the Commands tree with three or four named sections, one expanded and the others collapsed. Note: the old image is actions/flow/section.png.

Parameter	Description
Section name	Label shown on the collapsed group.

Comment

Inserts a note for yourself or your colleagues. Has no effect on execution.

📸 Screenshot needed — /img/editor/actions/project/comment.png

Capture: the Comment form with a multi-line note, plus how it renders in the tree. Note: the old image is actions/flow/comment.png.

Parameter	Description
Comment	Free-form text.

tip

Comment the why, not the what — the action list already says what happens. "This dialog only appears on the first login of the day" is worth writing down; "clicks OK" is not.

Input Form

Pauses the run and asks the person at the keyboard for values, which are then available as variables. Use it for the inputs that cannot be known in advance — a date range, a customer number, a one-off file path.

📸 Screenshot needed — /img/editor/actions/project/input_form.png

Capture: two images — the Input Form action form with several rows in Input Values (name + type per row), and the dialog the operator actually sees at runtime. Why it is new: this action did not exist in 0.14.2.

Parameter	Description
Input Values	The fields to ask for. Each row is a variable name plus its type — string, integer, float, boolean or a file path.
Require All Values	When on (default), the action fails if the operator leaves every field empty. (Advanced options)

warning

Input Form blocks the run until somebody answers it. A scheduled, unattended scenario will sit there until it times out — keep interactive forms out of anything the Orchestrator runs, or gate them with Enabled (Test) so they only appear while you are developing.

Import Scenario

Imports actions from another scenario file into this one — the way to reuse a login sequence or a shared cleanup routine across projects.

📸 Screenshot needed — /img/editor/actions/project/import_scenario.png

Capture: the Import Scenario form with a .json path selected. Note: the old image is actions/import/import_scenario.png.

Parameter	Description
Scenario File Path	Path to the .json scenario file to import.