Text
See also: Value from localization
Resolver – Abstract
Purpose: Defines a static text value (String) in the context of a value configuration.
►IMPORTANT◄ All resolvers for Static values ignore the input value. Within a resolver chain (see Verketteter Wertauflöser) this prevents the processing of all preceding resolvers (if any).
The Text resolver defines a static text value (String) in the context of a value configuration.
It appears by default as a suggestion for value configurations from which a String value is expected.
►NOTE◄ Before each use of the Text resolver in a value configuration, it has to be evaluated whether the respective text value should be implemented statically or via a reference to the Localization or Company specific localization. Even if there is no acute need for a 'localization' in the sense of a specific expression of the static text for the Current locale in a session, the use of the Value from localization resolver should be considered to enable a later localization. Of course, there are also many uses for technical strings, such as defining parameters in a configuration (e.g. 'variable name' in the Variable resolver), raw data for a file (see File reference), or to define a data object (see JSON to object, etc.). For such content, there is the Text resolver.
Configuration
The Text resolver offers a Text field element with the display type 'multiline text' with the following properties:
|
|
Special case: Direct input for a text parameter
If a text value is expected for a parameter in the context of a configuration, which should be definable either as static text or by any other value configuration, the user interface initially offers a Text field for the direct input of static text.
Example: Default error message parameter in the Abort event action.
If direct input is used by entering static text into the Text field, then the input is assigned to a Text resolver as a text value in the background.
However, the Text resolver is typically not displayed even if static text is already defined:
Only a click on the small gray arrow at the bottom left of the Text field activates the usual display of the value configuration for the parameter:
A click on the [+] symbol on the right side of the value configuration allows access to the text in the Text resolver:
Example
In the context of event handling, an Abort is executed under certain circumstances, which displays a default error message (CORESYSTEM_BaseDataManager_uniqueKeyViolationWithField) to the user.
The localization of the error message uses a parameter ({0}), which in our context should be assigned a static text value ('GTIN'):
{
0
} must be unique.
Configuration:
The Abort event action is parameterized as shown on the right:
|
|
Runtime example:
For Current locale 'English' (en) with default locale:
For Current locale 'Deutsch' (de) with default locale: