2.36.24
Glossary
The words this guide uses, each with where it is explained. The Concepts chapter tells how the most important ones fit together.
| Term | Meaning |
|---|---|
| Abort | Stopping a run, or a trigger run, for good. See Abort. |
| Activity | One step of work in a process, from an integration module, run by an agent. See Activities and connections. |
| Agent | A computer that runs activities. See Agents, agent-pools and demands. |
| Agent-pool | A group of agents that work as one, and share their capabilities. See Agent-pools. |
| Array | A variable that holds a list of values. See Lists. |
| Capability | Something an agent has, such as a browser. See Capabilities. |
| Cancel node | Stopping a node that runs, or a failed round of a loop, so the run can go on. See Cancel node. |
| Check | The designer's check of a process, which lists its errors and warnings. See The check and Validation rules. |
| Collection | A list of items by key, kept by the organization for its processes. See Collections. |
| Connection | The settings for reaching another system, per environment. See Connections. |
| Counter | A number that goes up by one each time a process asks. See Counters. |
| Demand | Something an activity needs an agent to have. See Demands. |
| Diagnostics | Settings that make activities take screenshots for a while, to see what went wrong. See Diagnostics and screenshots. |
| Draft | The changeable copy of a definition, before it is published. See Draft. |
| Environment | A stage, such as Test or Production, with its own runs and data. See Environment. |
| Expression | A formula that works out a value during a run, such as concat("Hello, ", {Name}). See Expressions and Expression functions. |
| Form | A form people fill in during a run (a user task) or to start one (a form trigger). See Forms and user tasks. |
| Gateway | A node that chooses or splits the path a run takes. See Gateways and conditions. |
| Input | A value an activity needs. See Inputs. |
| Integration module | A package of activities, triggers, types and kinds of connection. See Integration module. |
| Issue | A problem Spider reports to the support desk, such as a failed run or an agent in maintenance. See Issues. |
| Link | The arrow from one node to the next. See Links. |
| Log | What a node of a run wrote while it ran. See Logs. |
| Loop | A node repeated for each item of a list. See Loops. |
| Maintenance | The state of an agent that takes no new work until someone takes it out. See Maintenance. |
| Milestone | A point a run reaches, shown with an icon on its page and in the run lists. See Milestones. |
| Node | One element of a process's diagram: an event, a gateway, an activity, a sub-process. See The nodes. |
| Output | A value an activity gives back, stored in a variable. See Outputs. |
| Package | The file a process definition is exported as, with a description of what it uses. See Export and import. |
| Parameter | A variable whose value is given when a run starts. See Parameters. |
| Process definition | A process as designed, with its versions and its draft. See Process definition. |
| Process run | One time a process ran. See Process run. |
| Production | The environment that does the real work. See Environments. |
| Publish | Turning the draft into a new version. See Version and publishing. |
| Report | An entry a run adds when something happened, with tags, for reporting. See Reports. |
| Retry | Running the failed nodes of a run again. See Retry. |
| Retry from here | Running a run again from an earlier node. See Retry from here. |
| Robot account | The Windows account an agent works under, to drive applications on a desktop. See Robot accounts. |
| Scheduled run | A run that waits for the time it was given to start. See Scheduled runs. |
| Screenshot | A picture of the agent's screen, taken by an activity and shown in the run's log. See Diagnostics and screenshots. |
| Status | Where a run, a node, a trigger run or an agent stands. See Statuses. |
| Sub-process | A process inside a process, with its own diagram. See Sub-processes and loops. |
| Template | A text, such as an e-mail's body, with places where a run fills in its values. See Templates and e-mail. |
| Trigger | What starts runs by itself. See Triggers. |
| Trigger run | One time a trigger fired. See Trigger run. |
| Type | The kind of value a variable holds. See Types. |
| User task | A step of a run that waits for someone to fill in a form. See User tasks. |
| Variable | A named value a run works with. See Variables and parameters. |
| Version | A published state of a definition, such as 1.0. See Version and publishing. |