Process engine (SGU™) terms

Process holder: A process holder contains multiple BPMN processes (main process, swimlanes and embedded subprocesses) and variable definitions. The holder allows for multiple revisions (one in elaboration or testing, one in production and multiple obsolete revisions).

Process holder revision: A single revision of a process holder containing the processes and variable definitions.

Bpmn process: A single BPMN process (Note that tecnically enbedded subprocesses count as a separate process attached to the revision and connected to the sub process activity).

Bpmn process object: Generic term for any bpmn process element barring connections (for example activities, gateways, events and artifacts are bpmn process objects and the arrows between them are not).

Bpmn process object connector: The arrows between the bpmn process objects.

Bpmn loop characteristics: An indicator that forces the activity to itterate on itself until an excape condition becomes true. Each iteration instances a new token process object (and so becomes an independent task to resolve).

Bpmn loop characteristics rule: The rule that excapes the activity self loop.

Token process: An instance of a bpmn process execution. It contains many variable instances (the data generated by the process execution and users), and many token process objects.

Token process object: An instance of a bpmn process object execution. It holds state information and "holds" position in that part of the flow. It also stores the variable information as it was when the flow exited that object (automatically preserving variable history).

Variable definition: Each variable definition has a name and defines one or more attributes. It may also define relations to other variables. A variable definition that is not used in any other variable's definition is considered a base variable definition, otherwise it is an attacheable variable definition.

Root Variable Used refer to refer to variable definitions that sit at the base of the variable tree, these definitions only produce a single variable each (there cant be two instances of the same root variable definition). That is why the term "Root variable" is used interchangeably to refer both to the definition and to the instance throuought the documentation.

Variable definition relation: Defines how many instances of a given variable definition (one or multiple) may be attached to the variable instance (of the using variable definition).

Variable instance: Instance of a variable definition created during the execution of a token process. This is the actual object that carries the attribute values.

WeFlow™ terms

Component: Generic term for all WeFlow "pieces". Each component may have inputs, data (the options on the component), and outputs.

Input: Entry point for a component, accepts whatever data type defined by it's socket, inputs may only connect to outputs.

Data (or options): Options specific to a given component, allow for configuring what that component does.

Output: Exit point for a component, outputs whatever data type defined by it's socket, outputs may only connect to inputs.

Socket: Each input or output has a socket. The socket defines the data type that is allowed for that input or output.

Arithmetic: Components that perform mathematical operations.

Logic: Components that perform logical operations.