•Concepts and vocabulary

•Edge

Establishes a link between nodes to represent the workflow’s path.

•Node

Nodes are the building blocks of workflows. A node is a connector for sending and retrieving data, a function to process data, a nested workflow or a setter. By connecting multiple nodes, you can create simple or complex workflows. Each node must have a name. The default name is NewNode suffixed with the current node counter.

•Workflow

A workflow is a group of nodes connected together.

•Connector

Receives or sends data to/from external sources.

•Processor

You can use processors to transform or compute data, or even to perform more complex operations within workflows.

•Checkpoint

Snapshot of the project's state.

•Deployment

The process in which we upload the project to the production environment from a given checkpoint.

•Project

Projects allow you to group related workflows, connectors and processors together in a single workspace.

•Studio

Simple interface used to create workflows.

•Data Types

In order to achieve maximum security and reliability at runtime, Arbiter must know what data types are used. For technical readers - think of static typed languages. For the non-technical users an example will be the easiest way to clarify data types. Remember defining types correctly is one of the most important things in Arbiter.

•Input Parameters Form

You will see this form in a lot of places in the application. The available fields to populate are based on what is defined in the object schema.