Core concepts

Your workspace

Your enterprise is your customer workspace. It groups members, projects and shared defaults. A project contains related Jobs, Tasks, data definitions and collected results. Choose the correct project before editing or running work.

Your access determines which projects and commands you can see. A missing command may reflect your role or a project state rather than an application error.

The automation lifecycle

1. Create a Job with a name and scenario.
2. Open its Toolbox to edit and test actions.
3. Save the Job when the scenario is ready.
4. Launch a Session, or create a Task to launch it on a schedule.
5. Review the Session’s status, logs and results.

Term	Meaning
Job	A saved automation definition, including an ordered scenario.
Action	One instruction, such as navigating, typing, waiting or collecting a field.
Block	A branch or body containing actions under a control action.
Toolbox	An interactive authoring and testing workspace for a Job.
Task	A saved schedule associated with a Job.
Session	One accepted execution request and its execution history.
Attempt	One execution within a Session; retries create further Attempts.
Robot	The execution environment selected for the automation.
Container	A project definition describing collected records and fields.
Track	Collected structured information associated with a Container.
Settings	Configuration inherited through enterprise, project, Job and Task.

Testing and running

Toolbox testing keeps an interactive environment for successive commands. Apply action commits a pending form to the current scenario; Save persists the Job. Testing does not save either one automatically and creates no ordinary Session.

Debug is on by default: reached outer While/Repeat On loops advance once per Play, with nested loops completing. Debug off uses full traversal. Ordinary Sessions always use full traversal.

A Session uses the launch inputs and effective settings accepted for that execution. Later changes to defaults do not rewrite its captured settings. A retry starts again; it does not resume from the failed action.

Data, variables and files

Variables are working values used by actions. Collected data is structured output viewed under Data. Files are separate outputs such as captures or generated text documents. A value visible in Toolbox preview is not proof that a record or file was published. Some temporary Toolbox files can be downloaded while that environment remains available; they are separate from saved project Files.

Browser, HTML, Console and Desktop Linux have different capabilities. Choose the Robot kind before assuming a page, terminal or desktop action will work.