Terminology

A collection of automation scripts, corresponding libraries and other assets,

Combination of automation triggers, meta data and the code itself,

Automation scripts executed within a client’s browser,

Automation scripts executed inside the Corredor server,

A set of rules, constraints and options to define when, where and how an automation script is executed,

Defines the resource that this automation script is compatible with. It also defines the input and output of the automation script,

Defines what event causes this automation script to execute. For a full list of event types and availability based on the defined resource see @todo…​

A set of constraints that must be truthy in order for the automation script to be available and executable,

Allows us to specify the order of automation script execution for the given event,

Determine front-end aspects of the automation script invocation component; such as placement, label and color (see UIHooks),

Automation scripts that are executed explicitly, such as a button press or an API endpoint call,

Automation scripts that are executed implicitly as a collateral to an event, such as record creation and form submission,

Automation scripts that are executed at a specified time or on a configured interval,

Automation scripts that are executed over a larger set of resources at the same time (used for batch processing).

Automation scripts that are executed on HTTP requests and allow implementation of new endpoints,

Event handling system inside client web applications and on the server,

Define a front-end components that is used to execute explicit (manual) automation scripts (see UIProps).