Concat strings
Value resolver – Abstract
Purpose: Concatenates an arbitrary number of substrings, which can be defined by direct input or via value resolvers.
The Concat strings value resolver concatenates an arbitrary number of substrings defined by direct input – i.e. as static text (see Static values) – or by value resolvers.
The value resolver does not expect an input value. However, the input value can be accessed via value resolvers to define substrings.
Configuration
The value resolver does not contain any configurations for substrings by default.
Clicking the
icon adds a new instance for configuring a substring (below the current instance, if necessary).Clicking the
icon removes the configuration for the current substring.
|
In the screenshot to the right, the Concat strings value resolver is used in concatenation with a static text value resolver that provides the string SCMU3216083 WHT/BLU 40ft as input value. The Concat strings value resolver demonstrates both variants for defining substrings:
►NOTE◄ Clicking on the small gray arrow at the bottom left of the window for direct input switches to the configuration view via a value resolver. |
|
►IMPORTANT◄ When a substring configuration instance is added, the configuration should also be completed.
As long as the direct input – as shown in the following screenshot – displays the text 'No value', the value resolver runs an error at runtime:
If, on the other hand, a configured value resolver returns the value 'No value' ($null), then no error occurs, but the substring is treated as an empty string.
If the return value for a substring is not a string according to its type, the string image of the return value is processed as a string.
Example
|
In the text of a message (see Show alert (Popup)), two sections from a given text are concatenated. On the screen shot on the right, for demonstration purposes, the input value (as in the example above) as static text (SCMU3216083 WHT/BLU 40ft) is provided via concatenation. The message should reflect on the one hand the BIC code of the container (the first 11 characters from the input value) and on the other hand the size of the container (the last 4 characters from the input value). Labels or semigraphics are 'interspersed' over statically defined substrings:
|
|
|
Runtime example: ►NOTE◄ Instead of the static input value, another 'data source' would of course have to be set up in a practical application. |
|
