Glossary


Term

Context

Meaning

Asynchronous

Programmatic processes

Processes which are not performed sequentially (one step after the other) but staggered in time. E.g. user queries or any communication to the server.

Selection field

User interface

A selection field is a field with predefined possible values.

See also: Combobox

Client object


A client object is a data object that exists only on the client side, i.e. it has no representation in the database (and is therefore not permanent). The structure (fields) is not predefined and depends on the context (e.g. in the Search builder or depending on the form data in a workflow).

Data object

Data persistence

In Lobster Data Platform / Orchestration, a data object or entity is an object that is kept in the internal database of Lobster Data Platform / Orchestration.

Data object examples:

  • Company

  • User

  • Address

  • Shipment

  • Manifest

  • ...

Entity

Data persistence

Synonym for data object.

FRE


Form Renderer (Editor) – The technology that displays configured forms. The editor is used to configure such forms.

GUI


Graphical User Interface: The user interface of an application.

Child

Hierarchical structures

An element that is subordinate to another element within a hierarchical arrangement of elements. (see also 'Parent').

Example: Sub-company B of company A is a child of company A. In this case, company A is a parent of B.

Login token


A generated string which is used to identify a guest user.

Example of a login token: EDC6881D-A6A2-CC54-55C0-8B801993EDFE

Meta exchange

System management

The mechanism for exchanging (import/export job) configurations between Lobster Data Platform / Orchestration systems.

Parent

Hierarchical structures

If an element A is parent to another element B, then A is a parent of its child B (see also child).

Projection

Queries

A selected field from a record.

Example: 'name1' from an address data object.

Template


A template or stencil

Example:

In the context of data input forms, a template provides a predefined view of the data fields of an entity, which can then be read or manipulated by the user.

Tupel

Queries/data processing

A defined set of properties.
In the case of a database query, a tuple differs from a data object because the latter can only be a subset of one or more data objects.
A tuple is therefore not of any defined type.

e.g. Get 'username' a user and 'name1', 'name2' his address. This results in a tuple { username: "muha", name1: "Mustermann", name2: "Hans" }.

Inheritance

Rights/Properties

The transfer of properties, behaviours or rights, usually based on hierarchical relationships.

View


A view, overview or partial view of specific data or configuration options. This usually means forms and overviews, which are displayed in a window in the Lobster Data Platform / Orchestration interface.

Wildcard

Search/filter expressions

A wildcard in expressions (e.g. 'he*' is representative for all sentences/words that start with 'he', such as 'hello world', etc.