Lower case

See also: Upper case

Value resolver – Abstract

Purpose: Replaces all relevant characters of the string passed as input value with their equivalent 'in lower case'.


images/download/attachments/106957110/image2022-6-23_11-28-36-version-1-modificationdate-1655976516939-api-v2.png

The Lower case value resolver replaces all relevant characters of the string passed as input value with their equivalent in 'Lower case' letters.

NOTE

  • If there is no value ($null) as input value, the return value is also ($null).

  • For input values that are not strings, their string mapping is processed.

  • The value resolver generates the return value via the Java function toLowerCase(), which is then executed without explicit reference to a specific Locale. In this respect, the replacement scheme for the Locale defined by the execution context of the Lobster_pro server takes effect. For example, if the server is operated in an environment in the Turkish Locale (TR), the character 'I' is replaced by the character 'ı' and not by the otherwise common ' i ' .

  • There are special lowercase letters, such as the 'ß' in German, which are matched in uppercase by several characters ('SS'), which in turn are matched by another lowercase letter ('s'). The Kleinbuchstaben value resolver replaces each character individually in such cases (i.e.: 'SS' → 'ss') and not the group ('SS' → 'ß').

Configuration

The Lower case value resolver expects a string as input value and does not use any parameters.

Example

An event handler uses master data for the configuration of an IT system to calculate the storage capacity available for user data for this system and outputs this in a notification.

The relevant information in the master data is given as a 'Unit number', where the dynamic enumeration Size unit provides the units (TB, GB, MB, ...) and conversion rules.

The automatic string conversion for a 'Unit number' uses the localization texts for the corresponding dynamic enumeration values for the unit, i.e. by default plain texts like 'terabyte', 'gigabyte', 'megabyte'. However, instead of these texts, the respective 'alias' (TB, GB, MB, ...) appears in the output message, but explicitly in lower case letters.

Runtime example:

images/download/attachments/106957110/image2022-6-23_10-51-27-version-1-modificationdate-1655974288062-api-v2.png

Configuration:

The calculated value for the 'Available memory' is present in the context of an Execute with event action (not in the image) as an alternative reference object. Within the configuration for the Show alert (Popup) event action shown on the right, the 'Value' (value) and 'Unit' (unit) components are prepared individually and connected via a Concat strings value resolver:

  • The desired Format number is generated as text from the 'Value' (value) by a format number value resolver. For example, the thousands separator can be inserted and the number of decimals can be defined.

  • After an inserted space, the output for the 'Unit' (unit) prepared according to the request follows. Here the alias field from the definition for the unit that applies to the calculation result is accessed. The concatenated Lower case value resolver forces the alias to be output in lower case letters.

images/download/attachments/106957110/image2022-6-23_11-30-20-version-1-modificationdate-1655976620688-api-v2.png