Static values
'Static values' in Lobster Data Platform / Orchestration are values that are exclusively and directly defined by the configuration. Borrowing from the term 'hard coded' – 'static values' in Lobster Data Platform / Orchestration could also be referred to as 'hard-configured'.
The technical basis for a 'static value' in a value configuration is always the same 'literal value resolver' (LiteralValueResolver), which defines exactly one value (value) with one of the following 'data types':
|
|
Since a specific user interface is displayed for each data type and the selection of the data type for a static value works like the selection of a value resolver (see screenshot), the documentation describes the type-specific characteristics as if they were independent value resolvers. So, for example, when we talk about a 'Text', we actually mean a 'literal value resolver' for the definition of a text value.
The Static enumeration and Dynamic enumeration data types have a special position, because they appear as menu items under 'Static values' only if the context of a value configuration refers to a specific enumeration. Then the 'literal value' value resolver with a specific user interface is automatically suggested for the specific enumeration type (see Static enumeration or Dynamic enumeration, respectively) and all other options appear in the 'Unmatching/Static values' category of the context menu.
If an enumeration value is defined in a context as a static value that does not specify a reference to a specific enumeration, the Any static enumeration or Any dynamic enumeration menu option must be selected, depending on the category of the enumeration, in order to be able to select the desired value from a list of all enumeration values for the category.
Further configuration options for more complex 'static' values
The following configurations could be called 'static values' in a broader sense, which the 'literal value' value resolver does not directly cover:
Statically defined references to Company accounts or Roles
For 'static references' to Company accounts or Roles – e.g. in the context of Association criteria, Event handling or the Search API – Lobster Data Platform / Orchestration provides designated value resolvers (Company value and Role), which allow a static selection of exactly one instance of the respective entity.
Example:
|
A special custom overview for Users (see Custom overviews) should only list Users whose account is linked to a specific role on the one hand and to a specific company on the other hand. The screenshot on the right shows how the corresponding 'restriction' can be implemented in the definition of the custom overview:
►NOTE◄ The comparison ('==') is considered to be fulfilled if the list contains the compare value. It may therefore contain other values as well. |
|
►IMPORTANT◄ Static references to Company accounts and Roles should always be made via these value resolvers, if possible, with regard to the interpretation of links in the Meta exchange (for the exchange of configurations between systems). Like all other entities, Company accounts and Roles can also be addressed by ID, i.e. by Longvalue. However, it must always be kept in mind that the IDs of corresponding entities may differ on different systems and that an indirect reference via static Long is not adapted to any existing links between IDs.
Statically defined 'Unit number'
A statically determined 'Unit number' can be defined using the Calculate value value resolver with a calculation expression that associates a constant numeric value with the alias of the desired unit.
Example:
As a static 'Unit number', the volume of a gross register ton is defined using the Volume unit 'cubic feet' (with the alias ft3) previously defined as a user-defined volume unit. By definition, 100 cubic feet is equal to one gross register ton.
Static defined 'List'
If only 'Static values' are configured as entries in a Create list value resolver, the result could be called a 'static list'.
Example:
A 'static list' of 'keywords' defined over multiple instances of the Text value resolver are passed as selection options for a context menu:
Static defined 'object'
Any 'statically defined' data object can be created starting from a statically defined text using one of the following value resolvers:
Example:
In a context menu, the options 'STOP', 'HOLD' and 'GO' should appear in connection with an appropriately colored icon in the style of a traffic light.
|
In the Root items parameter of an Show context menu event action, the context menu is defined using a 'static list object' that contains objects with the 'option' and 'icon' fields as entries. Starting from a Text value resolver that statically defines a suitable JSON structure, the object for the context menu can be immediately and legibly 'tailored' in JSON and then generated using the concatenated JSON to object value resolver. The Label expression is obtained from the option field. The Icon expression is obtained from the icon field. The object defined line by line serves as a return value when an option is selected. It could contain further fields. Runtime example: (context menu)
|
|
